deploy-policy article complete

This commit is contained in:
Paolo Matarazzo
2023-03-07 09:08:24 -05:00
parent d69eb8c071
commit 7ab1b389d5

View File

@ -1,27 +1,25 @@
---
title: Sign and deploy policies for applications
description: Learn how to sign and deploy the policies for applications.
ms.date: 03/03/2023
title: Deploy policies to enable applications
description: Learn how to sign WDAC policies and how to deploy WDAC and AppLocker policies to enable apps execution on Windows SE devices.
ms.date: 03/07/2023
ms.topic: tutorial
appliesto:
-<a href="https://learn.microsoft.com/windows/release-health/supported-versions-windows-client" target="_blank">Windows 11 SE, version 22H2 and later</a>
---
# Deploy policies for applications
# Deploy policies to enable applications
This tutorial shows you how to deploy policies for applications.
Once the policies are created, you must deploy them to the Windows SE devices.
WDAC and AppLocker policies can be deployed via Intune, but WDAC policies must be signed before they can be deployed.
## Sign and deploy WDAC supplemental policies
This article describes how to sign WDAC policies and how to deploy WDAC and AppLocker policies to enable apps execution on Windows SE devices.
### Sign WDAC policies
## Sign WDAC supplemental policies
Follow the instructions below when you want to sign and deploy your WDAC supplemental policy.
> [!IMPORTANT]
> *This section will be updated when the process using Azure CodeSigning for CI policy is released in April.
- Create a supplemental policy with the instructions found above
- Sign the policy
- Deploy the signed policy file via Intune
### Deploy WDAC policies
## Deploy WDAC supplemental policies
Policies can be deployed via Intune using a custom OMA-URI.
@ -32,14 +30,14 @@ Policies can be deployed via Intune using a custom OMA-URI.
### Troubleshoot WDAC policies
For information how to troubleshoot WDAC supplemental policies, see [WDAC supplemental policy validation](./troubleshoot.md#wdac-supplemental-policy-validation)
For information how to validate and troubleshoot WDAC supplemental policies, see [WDAC supplemental policy validation](./troubleshoot.md#wdac-supplemental-policy-validation)
### Deploy AppLocker policies
Intune doesn't currently offer the option to modify AppLocker policies. The deployment of AppLocker policies can be done using PowerShell scripts deployed via Intune.
You can create a PowerShell script that stores the contents of the policy in a variable, then use the Set-AppLockerPolicy command to merge it in. Here's a sample function that does that:
You can create a PowerShell script that stores the contents of the policy in a variable, then use the `Set-AppLockerPolicy` PowerShell command to merge it. Here's a sample function for the task:
```PowerShell
function MergeAppLockerPolicy([string]$policyXml)
@ -54,14 +52,13 @@ function MergeAppLockerPolicy([string]$policyXml)
> **Warning**
>
> Intune deploys a script with the AppLocker policy to set Intune Management Extension as a managed installer on all Windows 11 SE devices enrolled into an Intune EDU tenant. If an EDU customer wishes to deploy their own AppLocker policy to set another Managed Installer (in addition to Intune), please be sure to ensure the `-Merge` parameter is used with `Set-AppLockerPolicy`. This will ensure that it plays well with Intune's AppLocker policy. Without using the `-Merge` parameter when deploying to Windows 11 SE devices, it will result in issues with apps getting tagged properly and their ability to run on impacted devices. Learn more about AppLocker Merge policy: Merge AppLocker policies by using [Set-ApplockerPolicy (Windows) | Microsoft Learn][WIN-7]
> Intune deploys a script with the AppLocker policy to set **Intune Management Extension as a managed installer** on all Windows 11 SE devices enrolled into an Intune EDU tenant. If you want to deploy your own AppLocker policy to set another Managed Installer (in addition to Intune), be sure to use the `-Merge` parameter with `Set-AppLockerPolicy`. The `-Merge` parameter ensures that your policy plays well with Intune's AppLocker policy. Without using the `-Merge` parameter, it will result in issues with apps not getting tagged properly and their ability to run on impacted devices. To learn more about AppLocker Merge policy, see [Merge AppLocker policies][WIN-7].
Once finished, you can deploy the script via Intune. For more information, see [Add PowerShell scripts to Windows devices in Microsoft Intune][MEM-1].
### Troubleshoot AppLocker policies
For information how to troubleshoot AppLocker policies, see [WDAC supplemental policy validation](./troubleshoot.md#applocker---msi-and-script)
For information how to validate and troubleshoot AppLocker policies, see [WDAC supplemental policy validation](./troubleshoot.md#applocker---msi-and-script)
## Next steps
@ -71,19 +68,15 @@ For a WDAC supplemental policy:
> [!div class="checklist"]
> - Signed .cip .p7b file with Device Guard
> - Targets Base policy: `82443e1e-8a39-4b4a-96a8-f40ddc00b9f3`
> - Policy created in Intune and assigned to the correct groups
> - Policy applied in Event Viewer
For an AppLocker policy
For an AppLocker policy:
> [!div class="checklist"]
> - Only applied to an updater or installer
> - Merge option used
> - Policy created in Intune and assigned to the correct groups
Advance to the next article to learn how to troubleshoot common errors when deploying apps with managed installer.
Advance to the next article to learn about important considerations for your tenant when deploying apps and policies to Windows SE devices.
> [!div class="nextstepaction"]
> [Next: deploy policies >](deploy-policies.md)
> - [Considerations for your tenant](considerations.md)