Approved Azure subscription not visible in portal (CPMD-Data-Automation)

Question

I created an internal Azure subscription named CPMD-Data-Automation for my organization. The subscription request was fully approved by both the budget owner and the service owner more than 36 hours ago.

However, the subscription is still not visible in the Azure portal and does not appear in the subscription selection dropdown. Because of this, I am unable to proceed with purchasing Microsoft Fabric capacity, which is blocking next steps for my work.

I would like to confirm whether this is a provisioning delay or if there are any additional actions required from my side for the subscription to become visible.

Answer 1

Hello Boris Gonsalves

Thank you for posting your query on Microsoft Q&A platform.

An approval alone does not guarantee immediate portal visibility. In almost all cases like this, the root cause falls into one of the following three areas, not a Fabric-specific issue:

1. Azure subscriptions are tied to one Microsoft Entra tenant.

Even after approval, the subscription will not appear if you are signed into a different directory.

• In Azure Portal (top‑right avatar) → Switch directory
• Select the tenant where the subscription request was created
• Go to Subscriptions and refresh

This is the most common reason for “approved but not visible” scenarios.

2. Global / local subscription filters hiding it:

The Azure portal can silently hide subscriptions due to filters.

What to check

• Azure Portal → Subscriptions
• Clear all filters
• Disable “Show only subscriptions selected in the global filter”
• Apply and refresh

Subscriptions can exist and be active but remain hidden by filters.

3. RBAC not yet applied to your user:

Approval does not automatically grant portal visibility unless RBAC is assigned.

If your account does not yet have Owner / Contributor / Reader on the subscription, it will not appear.

What to verify

• Ensure your user is explicitly assigned a role on CPMD‑Data‑Automation
• This must be done by someone who already has access

Azure AD / Entra roles alone (including Global Admin) are not sufficient.

To confirm whether the subscription actually exists:

Run this from Azure CLI:

az account list --output table

• If it appears in CLI but not in the portal → portal visibility / filter issue
• If it does not appear at all → provisioning or tenant association issue

If it still doesn’t appear, raise a billing support request with the approved subscription request ID.

If the provided information is helpful please click "upvote".

If you’re still experiencing the problem or need further clarification, please feel free to share additional information so we can continue investigating and assist you further.

Thanks,

Suchitra.

Answer 2

Based on the described symptoms, there are three main areas to check before assuming a backend provisioning delay:

1. Verify the correct directory and filters in the Azure portal
   Even when a subscription is created and active, it can be hidden by directory or filter settings:
   • In the Azure portal, select the account avatar (top-right) and confirm that the correct Microsoft Entra directory (tenant) is selected. If not, use Switch directory and recheck the Subscriptions blade.
   • Go to Subscriptions and clear any filters:
     1. Select Subscriptions in the portal.
     2. At the top of the list, select the Subscriptions filter item.
     3. In the filter box, select All, and clear Show only subscriptions selected in the global subscriptions filter.
     4. Select Apply and confirm whether CPMD-Data-Automation appears.
        Also ensure the global subscription filter is not hiding the subscription when using other blades.
2. Confirm directory/permissions and role assignment
   If the subscription exists but is not visible to the current account, it is commonly due to directory or RBAC issues:
   • Confirm again that the directory where the subscription was created is the one currently selected in the portal.
   • If the directory is correct but the subscription still does not appear, ensure that the account has at least Owner (or equivalent) on that subscription. If not, an admin with access must assign the appropriate role.
3. Check for pending cross-tenant subscription creation requests
   If the subscription was requested for a different tenant (for example, a customer or another internal tenant), the request might still be in a pending state:
   • In the billing/admin tenant where the request was initiated, go to Subscriptions → View requests.
   • Locate the creation request for CPMD-Data-Automation and check its status.
   • If the subscription is being created in another tenant, the designated subscription owner in that target tenant must accept ownership via the email link sent to them. If they have not accepted within seven days, the request expires and must be recreated.
   • From the request details, the Accept ownership URL can be copied and manually shared with the subscription owner to complete the process.

If all of the above are correct (right directory, filters cleared, correct permissions, and no pending/expired cross-tenant request) and the subscription still does not appear more than 24–36 hours after approval, this is likely a backend provisioning or account-level issue. In that case, raise a support request from the Azure portal so the Azure support team can check for account flags or incomplete subscription creation on the billing side.

---

References:

• Create an Enterprise Agreement subscription
• No subscriptions found sign in error for Azure portal
• EA Billing administration on the Azure portal
• Private offer troubleshooting
• Get subscription and tenant IDs in the Azure portal
• Message appears when you try to create multiple subscriptions

AI-generated content may be incorrect. Read our transparency notes for more information.