The purchase process creates an Azure-managed resource group in the background to host the OracleSubscription resource used for Oracle AI Database@Azure billing and subscription integration. Microsoft specifically documents a known issue in which Azure Policy can block this operation.

The system-created managed resource group must initially be located in EastUS , must conform to the provider-defined naming requirement, and is initially created without tags . Consequently, an enterprise policy that allows only West Europe or denies untagged resource groups prevents the OracleSubscription resource from being created. The correct remediation is to exempt the applicable managed resource group from those blocking policies during the purchase process. Microsoft recommends identifying the blocking assignment in the Azure activity log and creating an appropriate, preferably time-bound, Azure Policy exemption.

Administrators cannot solve the problem by manually creating their own resource group in West Europe because this is a provider-managed resource. Billing-address changes likewise do not change the resource provider's required deployment location, and OCI commercial-model changes do not remove the Azure OracleSubscription requirement.

Study Guide reference: Oracle AI Database@Azure Architecture and Onboarding — private offer purchase, OracleSubscription resource, Azure prerequisites and policy considerations.

===============