An Azure service that is used to collect, analyze, and act on telemetry data from Azure and on-premises environments.
Hello @Askardeen Buhari Thank you for posting your query on Microsoft Q&A platform.
New account shows existing subscriptions because this behavior is expected and is happening because both users are in the same Microsoft Entra ID (Azure AD) tenant.
Azure billing accounts are NOT the same thing as Azure AD tenants or user accounts.
When:
-
******@stoopa.aiand******@stoopa.aiboth exist in the same tenant (stoopa.ai), and -
******@stoopa.aiis added (directly or indirectly) to existing subscriptions or has inherited access,
then signing in with ******@stoopa.ai does not create a new billing account.
Azure simply:
- Logs the user into the same tenant
- Shows all subscriptions the user has access to
- Reuses the existing India-based billing account
This is why you’re not seeing a “fresh” US billing setup.
Recommended approach to create a truly US‑based billing account:
- To create a new US billing account, you must ensure billing isolation, not just a new user.
Supported and reliable options:
Option A (Most common / recommended)
- Create a new Azure billing account under Microsoft Customer Agreement (MCA) with:
- Country/Region = United States
- US payment method
- US sold‑to address (Georgia)
- This can be done in the same tenant or a separate tenant
- Then transfer subscription billing ownership from the India billing account to the US billing account
- US payment method
- Country/Region = United States
Option B (Strict separation)
- Create a new tenant
- Create the US billing account there
- Transfer subscriptions across billing accounts (and tenants if required)
Important: Creating a new user alone is not sufficient. Billing country is determined only at billing account creation time, not by user identity.
- When you transfer subscription billing ownership (India → US billing account):
Transfers automatically
- All Azure resources
- VMs, AKS, App Gateway, Storage, Databases, Networking, etc.
- Resource configurations
- Data and state
- Azure RBAC role assignments
- Managed Identities
- Service principals & app registrations
- Azure AD application permissions
Billing transfer does not move resources — it only changes who pays.
Below resources Does NOT transfer:
- Azure Support Plans
- Support plans are tied to the billing account
- Must be repurchased on the US billing account
- Billing history & invoices
- India invoices remain with India billing account
- US billing account starts fresh
- Tax profile
- India GST remains on historical invoices
- US tax rules apply only after transfer
- Azure DevOps clarification
- Azure DevOps organizations and projects are NOT impacted
- They are not tied to Azure billing accounts
- No reconfiguration required
- Manual reconfiguration required?
No, for Resources, Access, Identity, Applications, Data.
Yes, for Azure Support Plan (if needed)
- ADDITIONAL REQUEST: Can Microsoft assist with the transfer? Yes and this is strongly recommended
For production workloads, Microsoft does support assisted transfers.
You can:
- Open a Billing → Subscription transfer support request
- Request assistance for:
- Billing account validation
- Transfer execution
- Post‑transfer verification
- Transfer execution
- Billing account validation
Microsoft support can help ensure:
- No service interruption
- No permission loss
- Correct billing alignment
- Clean cutover from India → US tax jurisdiction
Important:
The transfer itself is non‑disruptive
Resources continue running throughout
Microsoft support involvement reduces operational risk
Thanks,
Suchitra.