Unable to create a Purview Account in another subscription.

Santhosh S V 0 Reputation points
2026-08-21T07:54:52.4033333+00:00

I am using one testing tenant for some poc, under that tenant i created one purview account service under subscription, now i tried to create another purview account in another subscription, but getting error like can't create more than one purview account in one tenant.

Could you please tell me how can i create another purview account in another subscription orelse any possible to delete existing purview account and create a new purview account in new subscription.

Microsoft Security | Microsoft Purview

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Himaja Y 280 Reputation points Microsoft External Staff Moderator
    2026-08-21T10:47:15.7766667+00:00

    Hi @Santhosh S V ,

    Thank you for reaching out to the Microsoft Q&A forum.

    The error is expected because Purview account creation is limited at the Microsoft Entra tenant level, not the subscription level.

    Tenant

    │

    ├── Subscription 1

    │ └── Purview Account 1 ✅

    │

    └── Subscription 2

    └── Purview Account 2 ❌

    Even though Subscription 2 is different, it is under the same tenant, so you cannot create another Purview account.

    Recommended solution:

    Don't delete the existing Purview account.

    Use the existing Purview account and create separate Collections for each subscription/POC:

    Purview Account

    │

    ├── Collection - POC 1

    │

    └── Collection - POC 2

    Then register the required data sources from both subscriptions and manage access using RBAC.

    If you need completely separate purview account, You would generally need a different Microsoft Entra tenant.

    Recommendation: For your POC, keep the existing Purview account and use Collections + RBAC to separate the environments.

    Was this answer helpful?

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.