Once reporting indicates the policy is applied successfully, it’s safe to unassign the original policy.If you change the assignment to use filters or to start with a test group, make sure the policy will eventually be assigned to all desired devices. If all settings are configured to the same value as the original policy, there won’t be any conflicts. Assign the policy to the same groups as the existing policy.Review the settings and values carefully as some of the names have been updated to match the exact Windows or Defender setting name.Create a new policy from the new template, ensuring the values exactly match those in the original policy.To move your policies, complete the following steps: However, you may choose to move your profiles over now. We’re automatically moving existing policies over to the new framework for you. If the policy type supports these devices, when it is migrated, it will begin applying to these devices. Important: Endpoint security policy on the unified settings platform supports Microsoft Defender for Endpoint security settings management. For example, when a policy is edited, reporting records of devices that have previously applied and reported on policy results but are no longer managed or checking in, won’t appear in the new reports until they check in again. Note that you may see a slight change in reporting numbers when these policies are migrated. We recommend switching to the new graph endpoints for policy creation as soon as possible. Once migrated, the new policies will have new PolicyIDs and will be created on the deviceManagement/configurationPolicies API. If you’re interacting with Endpoint security policies via the deviceManagement/templates or deviceManagement/intents Microsoft Graph API, you’ll be able to continue creating new policies, but they will be migrated later. If you do make a change, we’ll pause and restart the migration process for that policy.Īfter this migration, you’ll notice a new policy editing experience, improved reporting, and handling setting values of "not configured.” You’ll also be able to leverage new settings that have been added to these templates, scope tags, and assignment filters. You can still edit and interact with the policy even if you see the migration banner. This migration won’t impact your policies or the enforcement of the policies on your users' devices, as the configured settings and values will be moved over as they’re currently saved. Avoid editing policies as long as this message appears."Ī screenshot of the message the admin will see in the Endpoint security, Antivirus pane during the migration. During the migration, you may see the message stating, "Endpoint security profiles are being migrated to the unified settings platform. If you have Endpoint security policies configured from this time or before, you’ll be notified through the Message center. Policies created after April 2022 already leverage the unified settings platform. We’re migrating endpoint security policies created before April 2022, beginning with Microsoft Defender Antivirus policy. We’ve already published new templates as curated collections of settings for specific scenarios and baselines which are broader templates with the addition of recommended values for each setting.
Additionally, it provides consistency across naming, tooltips, and available values, and standardizes the “not configured” value for policy settings regardless of where you interact with the policy.
This platform is the foundation of the settings catalog, which provides quick access to policy and settings.
MICROSOFT INTUNE MANAGE WINDOWS UPDATES UPDATE
By: Mike Danoski – Senior Product Manager | Microsoft IntuneĪs we update and simplify creating and managing configuration settings in Microsoft Intune, we’re migrating policies and settings to the unified settings platform.
0 kommentar(er)
