For this chapter, you will need a modern web browser and a PowerShell code editor such as Visual Studio Code or PowerShell ISE.

All of the scripts referenced can be found here:

https://github.com/PacktPublishing/Microsoft-Intune-Cookbook/tree/main/Chapter2

Before following the following recipes, you may first need to re-authenticate to Microsoft Graph, as covered in Chapter 1.

Before moving on to configuring our policies, there are a couple of things to keep in mind.

Firstly, some settings can be configured in multiple places, especially when looking at security policies, so it is always worth keeping in mind what you are configuring and where to avoid making conflicting policies. Even if a setting has the same value in two different policies, it will be marked as a conflict within the GUI.

The other thing is the concept of tattooing. Some settings when applied can leave the setting configured on a device when switched to Not Configured within Intune. If there is a setting with the Enabled or Not Configured options, changing it to Not Configured does not send a signal to undo the configuration on the device; it simply tells Intune not to do anything with that particular setting and leave it to whatever happens to be set on the device already. Normally, this will just be the default Windows settings, but if it is a policy you have...

We will start with Settings catalog (or Unified Settings catalog) policies, which will be your primary policy type moving forward. Many of the older policies are being migrated to Settings catalog, and due to the nature of the Graph underneath these new policy types, this allows for significantly more available settings (there are well over 25,000 at the time of writing).

Settings catalog is also cross-platform and can be used for Windows, macOS, and iOS policies at present, with more being migrated daily. You will find the vast majority of your traditional on-premises Group Policy Objects (GPOs) here as well. If there is a setting you cannot find, there are other deployment methods, which will be covered in the following recipes.

As a Settings catalog policy can contain many thousands of policy settings, it can become more difficult to troubleshoot and slow to load and edit within a browser. Similar to when dealing with on-premises GPO,...

While the Settings catalog (and other options in the following recipes) will capture 99% of your needs in a standard environment, there may be times when you need to set CSP settings directly on machines and there is no template available.

For this recipe, we are going to use the policy that skips the User Settings section within the Enrollment Status Page (ESP) (there will be more on that in Chapter 4), which can be useful if you are happy that all of the key apps are targeted at the device setup and you do not want users to wait for the user-targeted apps to finish installing.

A custom Open Mobile Alliance Uniform Resource Identifier (OMA-URI) policy allows you to directly set the CSP settings, but you have to be careful that what you enter matches exactly what is expected, as these policies are very exact and will fail if a setting is incorrect.

Getting ready

As mentioned, for this example, we will skip the user status page, details of which...

A relatively new (and welcome) addition is the ability to ingest ADMX policies directly within the console. This is useful for your third-party products, which do not have policies configured within the Settings catalog and are easier to configure than custom OMA-URI policies.

Getting ready

For this example, we will use the Mozilla Firefox policy templates. The templates can be downloaded from this location: https://github.com/mozilla/policy-templates/releases.

The process is the same for any ADMX-based Architecture Description Markup Language (ADML), so feel free to use others if needed.

After downloading and extracting your templates, you will need firefox.admx and the matching ADML for your preferred language.

How to do it…

Follow this recipe to ingest and configure a policy for Mozilla Firefox:

1. Inside the Intune portal, navigate to Devices | Windows | Configuration profiles.

   At the top, next to where it says...

While it is generally recommended to create your new policies from scratch to reduce the amount of technical debt when migrating to Intune, you may have certain group policies configured in your on-premises Active Directory that you feel are good enough to be migrated directly to Intune. For this, we can use Group Policy analytics, which will ingest your policies, tell you which can be migrated, and also, if selected, migrate them for you.

Getting ready

The first thing we need is an XML export of the group policy we wish to inspect for compatibility with Intune. If you do not have a domain controller available, there is an example within GitHub here: https://github.com/PacktPublishing/Microsoft-Intune-Cookbook/blob/main/Chapter2/gpreport.xml:

1. Within Active Directory, navigate to Group Policy Objects:

Figure 2.11 – Group Policy Objects

2. Right-click on the Group Policy in question and click Back Up…...