From 9d66b4b22dfeda8955c113450bd1f50258530012 Mon Sep 17 00:00:00 2001 From: "Jason Jones (MSFT)" Date: Tue, 7 Oct 2025 12:37:21 +0100 Subject: [PATCH] Incorrect AppIdTaggingKey --- docs/external-id/tenant-restrictions-v2.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/external-id/tenant-restrictions-v2.md b/docs/external-id/tenant-restrictions-v2.md index 40efebe3693..62c0e374555 100644 --- a/docs/external-id/tenant-restrictions-v2.md +++ b/docs/external-id/tenant-restrictions-v2.md @@ -448,7 +448,7 @@ For more information, see [Creating your App Control AppId tagging policies](/wi After you create your policy in the wizard, or create your own by using PowerShell, convert the .xml output to an app ID tagging policy. The tagging policy marks the apps for which you want to allow access to Microsoft resources. The GUID output is your new policy ID. ```powershell - Set-CIPolicyIdInfo -ResetPolicyID .\policy.xml -AppIdTaggingPolicy -AppIdTaggingKey "M365ResourceAccessEnforced" -AppIdTaggingValue "True" + Set-CIPolicyIdInfo -ResetPolicyID .\policy.xml -AppIdTaggingPolicy -AppIdTaggingKey "M365ResourceAccessEnforcement" -AppIdTaggingValue "True" ``` #### Step 3: Compile and deploy the policy for testing