This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Choose the best response for each of the following questions.
Your data science team complains that Microsoft Foundry policies block their Azure OpenAI deployments for experimentation, slowing innovation. They request that you disable all governance policies for development subscriptions. Your compliance officer insists that data residency policies must apply everywhere. What approach balances these competing requirements?
Assign regional restriction policies in deny mode to all subscriptions to meet compliance requirements, but configure tagging and SKU policies in audit mode for development subscriptions so teams receive visibility without deployment blocking
Disable all policies in development subscriptions to maximize innovation velocity, then rely on monthly compliance reviews to identify and remediate any data residency violations that occurred
Apply all policies identically across development and production subscriptions using deny mode to ensure consistent governance, accepting that development velocity may decrease to maintain compliance
During a compliance audit, you discover that several Azure OpenAI deployments in your production subscription lack the required CostCenter tag, even though you assigned a tagging policy months ago. When you check Microsoft Foundry, the policy shows Active status with deny enforcement mode. What is the most likely cause of this compliance gap?
The tagging policy was assigned after the noncompliant resources were deployed, so existing resources weren't affected by the policy and only new deployments are evaluated
The policy enforcement mode was incorrectly set to audit instead of deny when it was assigned, allowing noncompliant deployments to proceed with warning logs
Microsoft Foundry policy evaluation experienced a service outage during the deployment window, temporarily bypassing policy checks for those specific resources
Your finance team reports that AI infrastructure costs exceeded the approved $20,000 monthly budget by 45% last quarter, despite budget alerts configured in Microsoft Foundry. Investigation reveals that teams received alert notifications but continued deploying resources because alerts don't prevent deployments. How should you strengthen cost governance while maintaining operational flexibility?
Implement Azure Policy definitions that deny creation of premium AI service SKUs (GPT-4, high-throughput instances) in all subscriptions, forcing teams to use cost-effective alternatives unless they request exceptions through a documented approval process
Configure spending limits at the subscription level that automatically suspend all deployments when the budget threshold is reached, preventing any resource creation until the next billing period
Transition budget alerts from notification-only mode to automated response mode that scales down or stops existing AI resources when spending reaches 90% of the monthly limit, preserving budget while maintaining deployed services
You must answer all questions before checking your work.
Was this page helpful?
Need help with this topic?
Want to try using Ask Learn to clarify or guide you through this topic?