Microsoft.Maps reports Registered but account creation returns InvalidSubscription

Your PAYG subscription reports Microsoft.Maps as registered, yet every creation path returns InvalidSubscription, so this is beyond a normal portal-display issue. Verify the active tenant and subscription with Azure CLI, then explicitly set the intended subscription. Query the Microsoft.Maps provider registration state and its account resource type, API versions, and locations. Retry one minimal creation using Gen2, G2, Global, and accepted terms; use a new resource name. Check the subscription Activity Log for the failed Microsoft.Maps/accounts write and retain the complete error details. Because Portal, CLI, and REST fail consistently after registration, more re-registration is unlikely to repair a backend entitlement problem. Open an Azure support request for Azure Maps/Resource Manager and supply the UTC timestamp, correlation ID, tenant, subscription, request API version, and operation log. Redact subscription and correlation identifiers from the public thread. Microsoft support must repair any provider entitlement inconsistency on the service side.

Seems the “InvalidSubscription” error when creating a Gen2 account indicates a mismatch between subscription eligibility and provider registration, may escalate with Azure Support to repair subscription metadata.