The ability to create Policy Sets came out in Intune in October 2019. This nice new feature allows you to group together different policies and applications and assign them to an Azure AD group. This post will show an example of creating a Policy Set for Windows 10 with a few policies and an app, and deploying it to an Azure AD group.
Policy sets known issues
You can include the following management objects in a policy set:
- App configuration policies
- App protection policies
- Device configuration profiles
- Device compliance policies
- Device type restrictions
- Windows autopilot deployment profiles
- Enrollment status page
At the time of writing this, you can see the Policy Sets in Intune in portal.azure.com but not in the M365 portal.
Click Create to create a policy set.
In my example, I am creating one for Windows 10.
If you look at the Known Issues link above, only these apps are supported for Policy Sets today:
iOS store app
iOS line-of-business app
Managed iOS line-of-business app
Android store app
Android line-of-business app
Managed Android line-of-business app
Office 365 ProPlus Suite (Windows 10)
Built-in iOS app
Built-in Android app
I have selected Office 365 then clicked Net.
I have selected some of my Device configuration profiles that I want to be applied:
I have assigned this to a group.
Once finished, click Review + create.
The device will apply the configurations from the Policy Set even if the individual apps and policies are not assigned to the group.
Policy Sets are still in preview at the moment and Microsoft will continue to improve them.
I recently ran into an issue where I was using Windows 10 Pro 1809 media and before “Account setup” step in the enrollment status page in Autopilot, I kept seeing the error “The parameter is incorrect”
This error only occurred for me in Windows 10 Pro 1809, and not in Windows 10 Pro 1903.
In the Event Logs in Applications and Services Logs > Microsoft > Windows > DeviceManagement-Enterprise-Diagnostics > Admin I saw:
MDM Session: Failed to get AAD Token for sync session User Token: (The parameter is incorrect.) Device Token: (Incorrect function.).
Long story short, I kept removing Device Configuration profiles I had assigned to the device, and the policy causing the issue was to upgrade Pro to Enterprise using an MAK key using the “Edition upgrade” policy.
To get rid of this error using Autopilot for Windows 10 Pro 1809, with a policy to upgrade to Enterprise, was to either use subscription based licensing assigned to the user, or to use Windows 10 Pro 1903.
The policy above caused a reboot on Windows 10 Pro 1809.
A reboot during Device setup will force the user to enter their credentials before transitioning to Account setup phase. User credentials aren’t preserved during reboot. Have the user enter their credentials then the Enrollment Status Page can continue.
Intune recently released the setting in the Administrative Templates to redirect known folders to OneDrive for Business.
This post will show how you can quickly configure it, and the user experience.
Login to the Intune portal https://devicemanagement.microsoft.com and create a new Device Configuration profile. Select Windows 10 and later for the platform, and Administrative Templates for the profile type.
Tip: there are many settings here. Use the search feature to make it easier.
Set the “Silently move Windows known folders to OneDrive” by selecting Enaled and enter in your Tenant ID. See below how you get the tenant ID.
To get your Tenant ID, go to Azure Active Directory, then Properties. Copy the Directory ID.
Configure the other settings such as “Silently sign in users to the OneDrive sync client with their Windows credentials”
Once you’re finished, don’t forget to assign the profile to your devices.
Here is an example of my Autopilot device applying the profile, and then the files appear on the desktop after OneDrive for Business has been configured.
Microsoft recently added “Require app protection policy (Preview)” to conditional access. App Protection Policies in Intune are a great way to secure the apps on either a managed device or an unmanaged device.
Suggested Reading – https://docs.microsoft.com/en-us/intune/app-protection-policy
This blogpost will show creating an example Conditional Access policy leveraging the “Require an app protection policy (Preview)” control, targeting Exchange Online, and the user experience for a device that does not have any App Protection Policies assigned.
In devicemanagement.microsoft.com go to Conditional Access, and create the new policy.
Give the policy a name, and in my policy I am testing out this policy, so I have only targeted one user.
I will be testing this policy only for Exchange Online.
I will only be using iOS and Android for this policy.
I have configured the conditions for all apps.
I have selected the control to require app protection policy.
The policy has now been created and enabled.
Below is the user experience when trying to add an email account targeted by the CA policy to the native mail app on an iOS device. You can see that it is blocked (similar to what happens if you require an approved client app in the CA policy)
Now If I try and setup the account in Outlook, I get the error saying that no application protection policies have been assigned.
In the Whats new Page for Intune (https://docs.microsoft.com/en-us/intune/whats-new), you can see that Microsoft recently added some BitLocker encryption reports in Preview.
For more information: https://docs.microsoft.com/en-us/intune/encryption-monitor
To access the Bitlocker reports, go to the Intune portal (portal.azure.com or devicemanagement.microsoft.com) and go to Device Configuration > Encyrption report (preview)
An example of the Bitlocker report is below:
You can also use the Filter button to filter the encryption readiness by Ready/Not ready and Encryption status by Encrypted/Not encrypted
The example below shows the devices that are not encrypted:
Recently when working with a customer I was troubleshooting why their devices were showing up as Azure AD Registered in the Azure portal in Azure Active Directory when they should be Hybrid Azure AD joined. These were Windows 10 1809 devices.
When running “dsregcmd /status” on one of the machines, it would show as AzureAdJoined : NO. When it is Hybrid Azure AD joined, it should still say Yes.
If you run the command as admin, you will see there is Diagnostic Data section. On my devices, it said:
Client ErrorCode : 0x801c03f2
Server ErrorCode : DirectoryError
Server Message : The device object by the given id (guid) is not found.
This is because the device(s) has not been synced to Azure AD by Azure AD Connect. Make sure that the OU’s that the computer objects are in are set to sync to Azure AD. In my customer’s configuration, they had additional filtering where the users and computer objects needed to be in a Security Group to be synced to Azure AD.
Once the Azure AD Connect sync had completed successfully, and the device registration task had run again on the client, the machine now shows as Hybrid Azure AD joined in the Azure portal.
When enrolling an iOS device in Intune, it may fail at the Installing Management Profile with the error “Intune – iOS – Profile installation Failed A connection to the server could not be established.”
If you happen to see this error, login to the Intune portal and go to Device Enrollment > Enrollment restrictions > and look through your existing restrictions to see if there are any settings blocking personal enrollments.
The example below shows that there is an enrollment restriction blocking personally owned iOS devices.
For the iOS to be enrolled, it needs to be a corporate owned iOS device. From https://docs.microsoft.com/en-us/intune/corporate-identifiers-add
At the time of enrollment, Intune automatically assigns corporate-owned status to devices that are:
- Enrolled with a device enrollment manager account (all platforms)
- Enrolled with the Apple Device Enrollment Program, Apple School Manager, or Apple Configurator (iOS only)
- Identified as corporate-owned before enrollment with an international mobile equipment identifier (IMEI) numbers (all platforms with IMEI numbers) or serial number (iOS and Android)
- Joined to Azure Active Directory as a Windows 10 Enterprise device
- Set as corporate in the device’s properties list