Friday, 7 August 2026

The documentation now explicitly states that Available assignments can target device groups for Win32 apps and apps targeting Android Enterprise fully managed (COBO) and corporate-owned personally enabled (COPE) devices. The documentation date changed from 12/03/2025 to 08/06/2026.

The article now retains the instruction to create an iOS app configuration policy but removes the linked Sophos Intercept X managed-settings reference.

The AIP mobile apps description no longer includes the sentence linking to Google Play for the mobile viewer app. The supported viewing description remains.

The BlackBerry Intune documentation no longer includes the link to BlackBerry UES documentation.

The protected apps reference no longer includes the Klaxoon for Intune entry.

The licensing documentation now states that Intune device-only subscriptions support eligible shared-device and no-user-affinity enrollment scenarios. It also clarifies that an unlicensed signed-in user does not prevent device-targeted policies, apps, or management actions from processing.

The macOS Automated Device Enrollment documentation now warns against targeting userless ADE devices with PSSO configuration profiles that enable PSSO registration during Setup Assistant. This can cause unexpected enrollment behavior and loss of expected device affinity.

The page now links only to the general Android and iOS store-app instructions; the direct CylancePROTECT Google Play and Apple App Store URLs were removed.

The page now notes that enrollment time grouping is available for iOS/iPadOS and macOS, along with the new Apple enrollment policies experience, and links to a previous blog post.

The page refreshes links for Intune App SDK certificate trust management, including the MAMCertTrustWebViewClient reference, which now points to GitHub documentation.

The setup page removes the external BlackBerry UES documentation link from step 8 and now instructs administrators to sign in with their Microsoft Entra account and complete setup.

The prerequisites documentation date changed from June 24, 2026 to August 6, 2026. It adds Red Hat Enterprise Linux 9.8 with Podman 5.8.2 or later as the default, noting that RHEL 9.8 does not automatically load the ip_tables kernel module.

The documentation now notes that collected registry key data is accessible through existing Device Inventory permissions and may expose sensitive device configuration information.

The Remediations link now points to the deploy-remediations.md page instead of deploy-remediations.

The government service page now lists Remediations, marked “n/a.”

The documentation now clarifies that MAA covers delegated actions and app-authenticated Microsoft Graph API calls when policies are already configured. It also documents per-policy enterprise application exclusions for app-auth calls, including a 50-application limit, second-admin approval, and audit logging.

The documentation now states that missing approval headers return HTTP 400, while a pending approval returns HTTP 412 (Precondition Failed) with a Microsoft Graph `BadRequest` code and an `x-msft-approval-code` header. It also instructs readers to save the original method, URL, and body for resubmission.

The sync page now states that its described behavior and Device sync status tab apply only to Windows devices, and instructs administrators to turn on the “Preview new device view” toggle in the top-right of the Intune admin center to see the new device sync improvements.

The What's new page now documents new Windows App and OneDrive settings, a package-removal subsetting, the Disable Get Started setting, and refreshed Visual Studio administrative templates including Disable MCP. These entries apply to Windows.

The custom role documentation now shows the Android Enterprise “Manage zero touch enrollment” permission and its Microsoft Intune admin center link.

The PKCS profiles article was updated with a note that device configuration profiles, including PKCS certificate profiles, aren’t supported on Microsoft Teams devices running AOSP. The document date changed from November 19, 2024, to August 6, 2026.

The documentation replaces the previous regional upload URLs with region-specific endpoint lists and directs administrators to Tenant Administration > Tenant Status in endpoint.microsoft.com to identify their tenant’s geo and data center.

The page title was capitalized and its description now states that it covers gathering hardware hashes and importing, editing, and deleting device records in the Intune admin center.

The documentation was updated to reformat three existing labels while keeping their names unchanged: M365-modern-desktop, m365initiative-coredeploy, and essentials-manage.

The endpoints documentation replaces the previous regional `lgmsape...blob.core.windows.net` entries with a larger list of `amsu...lmsas.blob.core.windows.net` endpoints.

The Service Connection Tool documentation updates the proxy example heading and command to use `itproxy.contoso.com:8080` instead of only the proxy hostname.

The documentation updates its date and clarifies that SQLSysClrTypes.msi and SharedManagementObjects.msi are no longer included in the Configuration Manager package. It also retains the update from SQL Server 2014 components to SQL Server 2025 versions (SMO 17).

The documentation now refers to the “CMG SUP server” instead of the “CGM SUP server” when configuring a boundary group.

The manual Azure AD app registration article no longer instructs administrators to set `oauth2AllowIdTokenImplicitFlow` to `true` in the app manifest. The article date changed from 03/11/2022 to 08/06/2026.

The version 2603 documentation clarifies that SQL Server Management Objects and SQL Server System CLR Types use the SQL Server 2025 versions (SMO 17), while the related MSI files are no longer included in Configuration Manager media.

The documentation now says Azure Virtual Desktop must be deployed in an Azure subscription associated with the same Entra ID tenant as Intune. The previous wording also referenced being in the same region.

The page title was capitalized, and its description now states that Software Center supports installing apps, software updates, and Windows upgrades, while directing users to the required setting.