Allow deployments only from Terraform using Azure Policy

Question

Allow deployments only from Terraform using Azure Policy

Logan 40

Hi Team,

Is it possible to block all deployments and allow it only from Terraform? I tried this but it didn't work.

{
          "not": {
            "anyOf": [
              {
                "field": "Microsoft.Authorization/roleAssignments/principalId",
                "equals": "[parameters('allowedServicePrincipal')]"
              }
            ]
          }
        }

Ashok Gandhi Kotnana 10,035 Reputation points Microsoft External Staff Moderator

2025-03-26T16:33:43.8633333+00:00

Hi @Logan,

There is an alternative way to achieve this requirement.

Grant all users read-only permissions, except for the service principal, which should be assigned Contributor access at the subscription level. This is the simplest way to meet your requirement.

If you prefer to enforce this via Azure Policy, note that there is no default policy available to achieve this. You will need to create a custom policy.

Please let me know if you're facing any challenges

If the answer is helpful, please and "Upvote it"
Logan 40 Reputation points

2025-03-26T16:43:26.45+00:00

Hi @Ashok Gandhi Kotnana , Thanks for the suggestion. We can't have this because there are some cases where we need to do the changes manually. Is there a field which can be verified by Azure policy when it's coming from Terraform or Manual or User deployment?
Ashok Gandhi Kotnana 10,035 Reputation points Microsoft External Staff Moderator

2025-03-26T17:22:13.2933333+00:00
Hi @Logan,

For the policy I cannot confirm as this is a custom policy this has to be tested before confirming with you

To identify who initiated a resource deployment:

Go to any Resource Group and check the Deployments section.

If the deployment name starts with "Microsoft.", it indicates that the resource was created via the Azure Portal, CLI, or PowerShell if it is terraform it won't show as Microsoft. this is one method to identity, but this is manual task

To automate this, update your PowerShell script in an Automation Account your script should get both values one if deployment name and resource

Please provide your thoughts.
Logan 40 Reputation points

2025-03-27T08:00:13.4233333+00:00

Hi @Ashok Gandhi Kotnana , Thank you. Actually, I'm looking for guidance on how to identify it using Azure Policy.

Checking if anyone come across this or have any thoughts on this requirement.?
Venkat V 2,545 Reputation points Microsoft External Staff Moderator

2025-03-27T15:17:44.24+00:00

Hi@Logan

The policy will only block or audit Azure resources because Terraform is an Iaac tool and there is no way to permit Terraform deployment from Azure policy.If you have a policy in place to block resources, it will prevent them from being created, whether they are in Terraform or other.

For example, if you made a policy to prevent RG names from beginning with Test, it will prevent if you used any source to create the RG.

Alternatively, you can assign the role only to the principal that you are using for deployment in Terraform. This ensures that only the service principal has access to create resources, and no other user or service principal can do so. This way, you restrict resource creation in Azure.
Venkat V 2,545 Reputation points Microsoft External Staff Moderator

2025-03-28T10:56:26.7966667+00:00

Hi@Logan

I just wanted to follow up and see if you had a chance to review my response to your question. Please let us know if it was helpful, and feel free to reach out if you have any further queries.
Logan 40 Reputation points

2025-03-28T11:21:26.6366667+00:00

Hi @Venkat V, Thanks for your comments. As it can block is there a way where we can block by identifying users or based on email address something?
Venkat V 2,545 Reputation points Microsoft External Staff Moderator

2025-03-29T03:18:33.3733333+00:00

Hi@Logan

Azure Policy applies only to management groups, subscriptions and resource groups. It is not possible to assign Azure Policy to a service principal. you can follow the Ms Doc for more information about Azure Policy assignment.

Azure Conditional Access policies in Azure AD can be used to block or restrict user access based on conditions such as user group membership, location, or sign-in risk. This allows you to set policies that limit access to resources based on the user's identity or email.

You could implement a custom solution using Azure Automation or Functions to monitor user activities or access patterns and take actions (like blocking users) based on your criteria (like specific email addresses or conditions).
Venkat V 2,545 Reputation points Microsoft External Staff Moderator

2025-04-01T09:55:01.7333333+00:00

Hi @Logan

I just wanted to follow up and see if you had a chance to review my response to your question. Please let us know if it was helpful, and feel free to reach out if you have any further queries.
Logan 40 Reputation points

2025-04-01T10:05:32.8366667+00:00

Hi Venkat V,

It wasn't very helpful, which is why I did some additional research but still couldn't find a solution. I understand that it's not available and we may need to think outside the box to figure out how we can prevent resource creation or modification, even if the user has permission to do so, but it should be only allowed from the Service Principal.

The reason I don't want to apply RBAC is that if the Terraform pipeline doesn't work, we might have to relax the policy and deploy it manually.
SadiqhAhmed-MSFT 49,326 Reputation points Microsoft Employee Moderator

2025-04-15T12:47:36.0666667+00:00

@Logan My sincere apologies for the delayed response!

From your post I understand that you want to allow deployments only through Terraform using Azure policy. You could leverage identity-based exemptions, which is currently in private preview, to achieve this scenario. With this, you’d be able to apply a policy to prevent resource creation or modification, then create an exemption for that assignment which would allow the Terraform pipeline’s Service Principal ID to bypass the policy. Refer to the document link - https://learn.microsoft.com/en-us/azure/governance/policy/concepts/exemption-structure for details on identity-based exemption private preview.

Let us know if you have any questions!
Logan 40 Reputation points

2025-04-16T16:59:58.8033333+00:00

Hi @SadiqhAhmed-MSFT

Looks like the link provided is incorrect or I can't see the identity-based exemption based references.
SadiqhAhmed-MSFT 49,326 Reputation points Microsoft Employee Moderator

2025-04-21T14:33:59.6666667+00:00

@Logan Sorry for the inconvenience. It is not in the public documentation yet because it is in private preview. The general structure of identity-based exemptions will look like this:

Example:
Assume you want to assign the built-in policy definition Allowed virtual machine size SKUs in your subscription to ensure that only A-family VMs can be deployed to keep cost down. You name the Policy assignment CostMgmt. However, certain engineers in your organization should be able to deploy higher-SKU, more expensive VMs for specific workloads and purposes. They should be able to bypass this policy. So, you create this exemption:

Now you’re all set! When a member of deploys a higher-SKU VM such as Standard_D1, they will not be blocked.

Hope this helps!
Logan 40 Reputation points

2025-04-21T14:48:15.19+00:00

Hi SadiqhAhmed-MSFT,

This is exactly what we wanted. Will i be able to test it in our tenant?
SadiqhAhmed-MSFT 49,326 Reputation points Microsoft Employee Moderator

2025-04-21T16:21:17.7166667+00:00

@Logan Yes, you can test it and let us know if you have any questions.

Logan 40

Hi SadiqhAhmed-MSFT,

I created a policy based on the template given but it is not working with any of the user id's.

Example: 1234-1234 is the my username object id and 3333-3333 is the test account. I tried with both accounts but no luck.

{
    "properties": {
        "policyAssignmentId": "/subscriptions/SubscriptionID/providers/Microsoft.Authorization/policyAssignments/DenyResourceCreation",
        "policyRule": {
            "if": {
                "field": "type",
                "equals": "Microsoft.Storage/storageAccounts"
            },
            "then": {
                "effect": "deny"
            }
        },
        "resourceSelectors": [
            {
                "name": "AllowedUsers",
                "selectors": [
                    {
                        "kind": "userPrincipalId",
                        "in": ["1234-1234"]
                    },
                    {
                        "kind": "userPrincipalId",
                        "notIn": ["1111-1111", "2222-2222","3333-3333"]
                    }
                ]
            }
        ],
        "exemptionCategory": "Waiver",
        "displayName": "Deny Resource Creation-v9",
        "description": "This exemption allows specific users to create resources"
    }
}

SadiqhAhmed-MSFT 49,326 Reputation points Microsoft Employee Moderator

2025-04-22T16:44:03.9+00:00

@Logan The sample you shared attempts to combine the identity-based resource selectors in the policy rule. However, the selectors belong in the exemption object, not in the policy definition.

So, you’ll first need to create the policy definition which blocks storage account creation, then assign it to the desired scope. Once that assignment is in place, then you’ll create an exemption for that assignment which uses selectors to specify allowed/disallowed user/object ID(s).

Also, in your selectors, it is not necessary to use both the “in” and “notIn” restrictions – this one is more restrictive and can be used by itself: "kind": "userPrincipalId", "in": ["1234-1234"]

Let me know if this makes sense.
Logan 40 Reputation points

2025-04-22T17:03:48.1333333+00:00

@SadiqhAhmed-MSFT, I was confused with your multiple screenshots and that's why added everything. If i understood correctly, I'll have to create block all users E.g group1 and create exemption for specific users. But i don't see any exemption for user-based category.

Only below are the exemptions available
SadiqhAhmed-MSFT 49,326 Reputation points Microsoft Employee Moderator

2025-04-23T05:26:17.2866667+00:00

@Logan Yes this [create block all users E.g group1 and create exemption for specific users] is the correct understanding. In its current private preview state, identity-based exemptions through resource selectors are not supported in portal. Can you try creating the exemption through an API call?
Logan 40 Reputation points

2025-04-23T09:59:08.3+00:00

Hi @SadiqhAhmed-MSFT , Are you sure through API we can exempt because i was referring this article and don't see the relevant exemption

https://learn.microsoft.com/en-us/rest/api/policy/policy-exemptions/create-or-update?view=rest-policy-2022-07-01-preview&tabs=HTTP

Can you please share the correct article.
SadiqhAhmed-MSFT 49,326 Reputation points Microsoft Employee Moderator

2025-04-24T16:38:54.13+00:00

@Logan This feature is not publicly documented yet because it is in private preview.

Since this capability is just an additional supported property (resourceSelectors) in the exemption JSON payload, all you have to do is adjust the request body for the create API call.

The screenshots I shared in the earlier post shows the JSON schema to use in the request body for the API call to create an identity-based exemption, and you can just use the existing URI (in the public document you linked) to send the create API request.

Sorry for the confusion here! Let me know if you have further questions.
Logan 40 Reputation points

2025-04-25T08:05:40.48+00:00

SadiqhAhmed-MSFT, Will you be able to provide any example?
SadiqhAhmed-MSFT 49,326 Reputation points Microsoft Employee Moderator

2025-04-28T07:22:47.2866667+00:00

@Logan YES – you should be able to create the exemption using an API request URI & request body like this (be sure to first assign the policy, then insert real values for the placeholders shown):

PUT https://management.azure.com/{scope}/providers/Microsoft.Authorization/policyExemptions/{policyExemptionName}?api-version=2022-07-01-preview

Let me know if this works out for you.
Logan 40 Reputation points

2025-04-29T17:19:39.0633333+00:00

This feature is exactly what I was looking for and it’s working as expected. Could you please let me know when it will be available for general use? Additionally, is there an RSS feed I can subscribe to so I can stay updated on its availability?

Just to give you a heads up, my company has a policy that restricts us from using any feature that is still in preview. So, I’d like to ensure we are compliant with this policy.
Logan 40 Reputation points

2025-05-02T12:55:56.5866667+00:00

@SadiqhAhmed-MSFT, Any update here?
guilherme rodrigues 390 Reputation points

2025-05-02T13:04:45.25+00:00

Hi, Logan!

It is not possible to fully manage deployment permissions using Terraform alone, especially when the goal is to restrict deployments to a specific service principal. Azure Policy does not have the capability to enforce policies based on who is performing the deployment action at runtime, it only evaluates the state of the resources being deployed or modified.

The best approach in this scenario is to manage access control through Azure RBAC (Role-Based Access Control). By assigning the required Contributor (or equivalent) role only to the Terraform service principal and limiting all other users/groups to Reader or minimal permissions, you can effectively ensure that only Terraform is allowed to deploy and modify resources.
Logan 40 Reputation points

2025-05-02T13:17:57.5833333+00:00

Hey guilherme rodrigues, Not sure why you're reinventing it again? because it's working using policies suggested by @SadiqhAhmed-MSFT
SadiqhAhmed-MSFT 49,326 Reputation points Microsoft Employee Moderator

2025-05-06T15:58:07.5866667+00:00

@Logan Great to hear it’s working for your scenario! The feature is fully supported at the API level but remains in private preview while we collect feedback on the experience and complete the necessary steps to release it in public preview or GA, including portal support. We don’t currently have an ETA for these releases, but we will be reaching out to customers using the private preview to keep you informed, and you can keep up with product announcements through blog posts.
SadiqhAhmed-MSFT 49,326 Reputation points Microsoft Employee Moderator

2025-05-07T19:50:53.96+00:00

@Logan Let us know if you have any questions. If no, then I would like to summarize the answer and post it as a solution to your ask. By "Accepting Answer" and "Voting it as helpful" can help closing this conversation and help others looking for a solution to similar scenario.
Logan 40 Reputation points

2025-05-08T08:15:37.5966667+00:00

@SadiqhAhmed-MSFT, Sure please go ahead and i'll mark it as answer. Once again thank you for your support.
SadiqhAhmed-MSFT 49,326 Reputation points Microsoft Employee Moderator

2025-05-08T19:35:51.65+00:00

@Logan Thanks for confirming. Glad to help! :)

Accepted answer

0 additional answers

Your answer

Ashok Gandhi Kotnana 10,035 Reputation points Microsoft External Staff Moderator

2025-03-26T16:33:43.8633333+00:00

Hi @Logan,

There is an alternative way to achieve this requirement.

Grant all users read-only permissions, except for the service principal, which should be assigned Contributor access at the subscription level. This is the simplest way to meet your requirement.

If you prefer to enforce this via Azure Policy, note that there is no default policy available to achieve this. You will need to create a custom policy.

Please let me know if you're facing any challenges

If the answer is helpful, please and "Upvote it"
Logan 40 Reputation points

2025-03-26T16:43:26.45+00:00

Hi @Ashok Gandhi Kotnana , Thanks for the suggestion. We can't have this because there are some cases where we need to do the changes manually. Is there a field which can be verified by Azure policy when it's coming from Terraform or Manual or User deployment?
Ashok Gandhi Kotnana 10,035 Reputation points Microsoft External Staff Moderator

2025-03-26T17:22:13.2933333+00:00

Hi @Logan,

For the policy I cannot confirm as this is a custom policy this has to be tested before confirming with you

To identify who initiated a resource deployment:

Go to any Resource Group and check the Deployments section.

If the deployment name starts with "Microsoft.", it indicates that the resource was created via the Azure Portal, CLI, or PowerShell if it is terraform it won't show as Microsoft. this is one method to identity, but this is manual task

To automate this, update your PowerShell script in an Automation Account your script should get both values one if deployment name and resource

Please provide your thoughts.
Logan 40 Reputation points

2025-03-27T08:00:13.4233333+00:00

Hi @Ashok Gandhi Kotnana , Thank you. Actually, I'm looking for guidance on how to identify it using Azure Policy.

Checking if anyone come across this or have any thoughts on this requirement.?
Venkat V 2,545 Reputation points Microsoft External Staff Moderator

2025-03-27T15:17:44.24+00:00

Hi@Logan

The policy will only block or audit Azure resources because Terraform is an Iaac tool and there is no way to permit Terraform deployment from Azure policy.If you have a policy in place to block resources, it will prevent them from being created, whether they are in Terraform or other.

For example, if you made a policy to prevent RG names from beginning with Test, it will prevent if you used any source to create the RG.

Alternatively, you can assign the role only to the principal that you are using for deployment in Terraform. This ensures that only the service principal has access to create resources, and no other user or service principal can do so. This way, you restrict resource creation in Azure.
Venkat V 2,545 Reputation points Microsoft External Staff Moderator

2025-03-28T10:56:26.7966667+00:00

Hi@Logan

I just wanted to follow up and see if you had a chance to review my response to your question. Please let us know if it was helpful, and feel free to reach out if you have any further queries.
Logan 40 Reputation points

2025-03-28T11:21:26.6366667+00:00

Hi @Venkat V, Thanks for your comments. As it can block is there a way where we can block by identifying users or based on email address something?
Venkat V 2,545 Reputation points Microsoft External Staff Moderator

2025-03-29T03:18:33.3733333+00:00

Hi@Logan

Azure Policy applies only to management groups, subscriptions and resource groups. It is not possible to assign Azure Policy to a service principal. you can follow the Ms Doc for more information about Azure Policy assignment.

Azure Conditional Access policies in Azure AD can be used to block or restrict user access based on conditions such as user group membership, location, or sign-in risk. This allows you to set policies that limit access to resources based on the user's identity or email.

You could implement a custom solution using Azure Automation or Functions to monitor user activities or access patterns and take actions (like blocking users) based on your criteria (like specific email addresses or conditions).
Venkat V 2,545 Reputation points Microsoft External Staff Moderator

2025-04-01T09:55:01.7333333+00:00

Hi @Logan

I just wanted to follow up and see if you had a chance to review my response to your question. Please let us know if it was helpful, and feel free to reach out if you have any further queries.
Logan 40 Reputation points

2025-04-01T10:05:32.8366667+00:00

Hi Venkat V,

It wasn't very helpful, which is why I did some additional research but still couldn't find a solution. I understand that it's not available and we may need to think outside the box to figure out how we can prevent resource creation or modification, even if the user has permission to do so, but it should be only allowed from the Service Principal.

The reason I don't want to apply RBAC is that if the Terraform pipeline doesn't work, we might have to relax the policy and deploy it manually.
SadiqhAhmed-MSFT 49,326 Reputation points Microsoft Employee Moderator

2025-04-15T12:47:36.0666667+00:00

@Logan My sincere apologies for the delayed response!

From your post I understand that you want to allow deployments only through Terraform using Azure policy. You could leverage identity-based exemptions, which is currently in private preview, to achieve this scenario. With this, you’d be able to apply a policy to prevent resource creation or modification, then create an exemption for that assignment which would allow the Terraform pipeline’s Service Principal ID to bypass the policy. Refer to the document link - https://learn.microsoft.com/en-us/azure/governance/policy/concepts/exemption-structure for details on identity-based exemption private preview.

Let us know if you have any questions!
Logan 40 Reputation points

2025-04-16T16:59:58.8033333+00:00

Hi @SadiqhAhmed-MSFT

Looks like the link provided is incorrect or I can't see the identity-based exemption based references.
SadiqhAhmed-MSFT 49,326 Reputation points Microsoft Employee Moderator

2025-04-21T14:33:59.6666667+00:00

@Logan Sorry for the inconvenience. It is not in the public documentation yet because it is in private preview. The general structure of identity-based exemptions will look like this:

Example:
Assume you want to assign the built-in policy definition Allowed virtual machine size SKUs in your subscription to ensure that only A-family VMs can be deployed to keep cost down. You name the Policy assignment CostMgmt. However, certain engineers in your organization should be able to deploy higher-SKU, more expensive VMs for specific workloads and purposes. They should be able to bypass this policy. So, you create this exemption:

Now you’re all set! When a member of deploys a higher-SKU VM such as Standard_D1, they will not be blocked.

Hope this helps!
Logan 40 Reputation points

2025-04-21T14:48:15.19+00:00

Hi SadiqhAhmed-MSFT,

This is exactly what we wanted. Will i be able to test it in our tenant?
SadiqhAhmed-MSFT 49,326 Reputation points Microsoft Employee Moderator

2025-04-21T16:21:17.7166667+00:00

@Logan Yes, you can test it and let us know if you have any questions.
Logan 40 Reputation points

2025-04-21T17:19:47.29+00:00

Hi SadiqhAhmed-MSFT,

I created a policy based on the template given but it is not working with any of the user id's.

Example: 1234-1234 is the my username object id and 3333-3333 is the test account. I tried with both accounts but no luck.

{ "properties": { "policyAssignmentId": "/subscriptions/SubscriptionID/providers/Microsoft.Authorization/policyAssignments/DenyResourceCreation", "policyRule": { "if": { "field": "type", "equals": "Microsoft.Storage/storageAccounts" }, "then": { "effect": "deny" } }, "resourceSelectors": [ { "name": "AllowedUsers", "selectors": [ { "kind": "userPrincipalId", "in": ["1234-1234"] }, { "kind": "userPrincipalId", "notIn": ["1111-1111", "2222-2222","3333-3333"] } ] } ], "exemptionCategory": "Waiver", "displayName": "Deny Resource Creation-v9", "description": "This exemption allows specific users to create resources" } }
SadiqhAhmed-MSFT 49,326 Reputation points Microsoft Employee Moderator

2025-04-22T16:44:03.9+00:00

@Logan The sample you shared attempts to combine the identity-based resource selectors in the policy rule. However, the selectors belong in the exemption object, not in the policy definition.

So, you’ll first need to create the policy definition which blocks storage account creation, then assign it to the desired scope. Once that assignment is in place, then you’ll create an exemption for that assignment which uses selectors to specify allowed/disallowed user/object ID(s).

Also, in your selectors, it is not necessary to use both the “in” and “notIn” restrictions – this one is more restrictive and can be used by itself: "kind": "userPrincipalId", "in": ["1234-1234"]

Let me know if this makes sense.
Logan 40 Reputation points

2025-04-22T17:03:48.1333333+00:00

@SadiqhAhmed-MSFT, I was confused with your multiple screenshots and that's why added everything. If i understood correctly, I'll have to create block all users E.g group1 and create exemption for specific users. But i don't see any exemption for user-based category.

Only below are the exemptions available
SadiqhAhmed-MSFT 49,326 Reputation points Microsoft Employee Moderator

2025-04-23T05:26:17.2866667+00:00

@Logan Yes this [create block all users E.g group1 and create exemption for specific users] is the correct understanding. In its current private preview state, identity-based exemptions through resource selectors are not supported in portal. Can you try creating the exemption through an API call?
Logan 40 Reputation points

2025-04-23T09:59:08.3+00:00

Hi @SadiqhAhmed-MSFT , Are you sure through API we can exempt because i was referring this article and don't see the relevant exemption

https://learn.microsoft.com/en-us/rest/api/policy/policy-exemptions/create-or-update?view=rest-policy-2022-07-01-preview&tabs=HTTP

Can you please share the correct article.
SadiqhAhmed-MSFT 49,326 Reputation points Microsoft Employee Moderator

2025-04-24T16:38:54.13+00:00

@Logan This feature is not publicly documented yet because it is in private preview.

Since this capability is just an additional supported property (resourceSelectors) in the exemption JSON payload, all you have to do is adjust the request body for the create API call.

The screenshots I shared in the earlier post shows the JSON schema to use in the request body for the API call to create an identity-based exemption, and you can just use the existing URI (in the public document you linked) to send the create API request.

Sorry for the confusion here! Let me know if you have further questions.
Logan 40 Reputation points

2025-04-25T08:05:40.48+00:00

SadiqhAhmed-MSFT, Will you be able to provide any example?
SadiqhAhmed-MSFT 49,326 Reputation points Microsoft Employee Moderator

2025-04-28T07:22:47.2866667+00:00

@Logan YES – you should be able to create the exemption using an API request URI & request body like this (be sure to first assign the policy, then insert real values for the placeholders shown):

PUT https://management.azure.com/{scope}/providers/Microsoft.Authorization/policyExemptions/{policyExemptionName}?api-version=2022-07-01-preview

Let me know if this works out for you.
Logan 40 Reputation points

2025-04-29T17:19:39.0633333+00:00

This feature is exactly what I was looking for and it’s working as expected. Could you please let me know when it will be available for general use? Additionally, is there an RSS feed I can subscribe to so I can stay updated on its availability?

Just to give you a heads up, my company has a policy that restricts us from using any feature that is still in preview. So, I’d like to ensure we are compliant with this policy.
Logan 40 Reputation points

2025-05-02T12:55:56.5866667+00:00

@SadiqhAhmed-MSFT, Any update here?
guilherme rodrigues 390 Reputation points

2025-05-02T13:04:45.25+00:00

Hi, Logan!

It is not possible to fully manage deployment permissions using Terraform alone, especially when the goal is to restrict deployments to a specific service principal. Azure Policy does not have the capability to enforce policies based on who is performing the deployment action at runtime, it only evaluates the state of the resources being deployed or modified.

The best approach in this scenario is to manage access control through Azure RBAC (Role-Based Access Control). By assigning the required Contributor (or equivalent) role only to the Terraform service principal and limiting all other users/groups to Reader or minimal permissions, you can effectively ensure that only Terraform is allowed to deploy and modify resources.
Logan 40 Reputation points

2025-05-02T13:17:57.5833333+00:00

Hey guilherme rodrigues, Not sure why you're reinventing it again? because it's working using policies suggested by @SadiqhAhmed-MSFT
SadiqhAhmed-MSFT 49,326 Reputation points Microsoft Employee Moderator

2025-05-06T15:58:07.5866667+00:00

@Logan Great to hear it’s working for your scenario! The feature is fully supported at the API level but remains in private preview while we collect feedback on the experience and complete the necessary steps to release it in public preview or GA, including portal support. We don’t currently have an ETA for these releases, but we will be reaching out to customers using the private preview to keep you informed, and you can keep up with product announcements through blog posts.
SadiqhAhmed-MSFT 49,326 Reputation points Microsoft Employee Moderator

2025-05-07T19:50:53.96+00:00

@Logan Let us know if you have any questions. If no, then I would like to summarize the answer and post it as a solution to your ask. By "Accepting Answer" and "Voting it as helpful" can help closing this conversation and help others looking for a solution to similar scenario.
Logan 40 Reputation points

2025-05-08T08:15:37.5966667+00:00

@SadiqhAhmed-MSFT, Sure please go ahead and i'll mark it as answer. Once again thank you for your support.
SadiqhAhmed-MSFT 49,326 Reputation points Microsoft Employee Moderator

2025-05-08T19:35:51.65+00:00

@Logan Thanks for confirming. Glad to help! :)

Answer 1

@Logan Thank you for reaching out to us and appreciate your patience during the support tenure through Microsoft Q&A platform.Sharing the summarized answer to help other community members/users looking for similar solution.

Question: Allow deployments only from Terraform using Azure Policy

Solution: You could leverage identity-based exemptions, which is currently in private preview, to achieve this scenario. With this, you’d be able to apply a policy to prevent resource creation or modification, then create an exemption for that assignment which would allow the Terraform pipeline’s Service Principal ID to bypass the policy.

So, you’ll first need to create the policy definition which blocks storage account creation, then assign it to the desired scope. Once that assignment is in place, then you’ll create an exemption for that assignment which uses selectors to specify allowed/disallowed user/object ID(s).

Also, in your selectors, it is not necessary to use both the “in” and “notIn” restrictions – this one is more restrictive and can be used by itself: "kind": "userPrincipalId", "in": ["1234-1234"]

[create block all users E.g group1 and create exemption for specific users] is the correct understanding. In its current private preview state, identity-based exemptions through resource selectors are not supported in portal. Try creating the exemption through an API call.

You should be able to create the exemption using an API request URI & request body like this (be sure to first assign the policy, then insert real values for the placeholders shown):

PUT https://management.azure.com/{scope}/providers/Microsoft.Authorization/policyExemptions/{policyExemptionName}?api-version=2022-07-01-preview

User's image

Note: The feature is fully supported at the API level but remains in private preview while we collect feedback on the experience and complete the necessary steps to release it in public preview or GA, including portal support. We don’t currently have an ETA for these releases, but we will be reaching out to customers using the private preview to keep you informed, and you can keep up with product announcements through blog posts.

If the response helped, do "Accept Answer" and up-vote it

Share via

Allow deployments only from Terraform using Azure Policy

0 additional answers

Your answer