Index
Doc updateThe page date changed to November 2, 2026, and the section announcing general availability of scoped permissions for role-based access control was removed.
3 November 2026
Week in brief
Multi-session Intune scripts now require device targeting in revised guidance
Microsoft’s changes this week are documentation-led. The most actionable Intune updates refine the documented assignment and execution model for PowerShell on Azure Virtual Desktop multi-session devices, add two MEM-Win32Apps hosts to endpoint guidance, and define the reporting limits for MDM-managed Firewall Rules and ASR Rules. Configuration Manager’s strongest update clarifies the TLS 1.2 client procedure, while other edits mainly refine console, co-management, tools, and index content.
- Azure Virtual Desktop scripts now use device targeting guidance
Intune · GeneralThe Azure Virtual Desktop multi-session guidance now requires PowerShell scripts to target devices. It also specifies setting Logged-on credentials to No for system context or Yes for user context. Review assignments and credential-context settings for multi-session scripts.
- Device-assigned scripts run for every new user sign-in
Intune · Device securityThe Windows PowerShell script guidance now states that scripts assigned to a device run for every new user who signs in, and removes the previous multi-session SKU exception. Recheck multi-session deployment plans against this documented execution model.
- MEM-Win32Apps endpoint guidance adds two blob hosts
Intune · FundamentalsThe endpoint list now includes mmcswdc01.blob.core.windows.net and mmcswdc02.blob.core.windows.net for MEM-Win32Apps alongside the existing hosts. Review network allowlists supporting Win32 app delivery and add the hostnames if required.
- MDM firewall and ASR policies report only at policy levelIntune · Device security
Security Settings Management guidance now states that per-setting reporting is unavailable for Firewall Rules and ASR Rules policies managed through MDM; only policy-level status is reported. Use policy-level status when reviewing these policies.
- Configuration Manager TLS 1.2 client steps are more clearly sequenced
Configuration Manager · GeneralThe client guidance now separates the three client-enablement tasks, refines the sequence for enabling TLS 1.2 and disabling older protocols, and updates .NET Framework wording and references. Use the revised procedure when configuring TLS 1.2 client readiness.
For Intune administrators
Review PowerShell assignments and credential-context settings on multi-session devices, validate Win32 app network allowlists, and use policy-level status when assessing MDM-managed firewall and ASR policies. For Configuration Manager TLS 1.2 work, follow the revised client-enablement sequence and framework guidance.
This period briefing was generated by AI from the tracked Microsoft Learn and Message Center changes.
Updates this week
Microsoft Intune
6 updatesAzure Virtual Desktop Multi Session
Feature updateAction requiredThe documentation now requires PowerShell scripts to be targeted to devices. Set logged-on credentials to No for system context or Yes for user context.
3 November 2026
Setup Mobile Threat Defense
Doc updateThe article’s reviewer changed from aanavath to ilwu.
3 November 2026
Security Settings Management
Doc updateThe documentation now states that per-setting reporting is unavailable for Firewall Rules and ASR Rules policies managed through MDM; only policy-level status is reported.
3 November 2026
Run Powershell Scripts Windows
Doc updateThe documentation now states that PowerShell scripts assigned to a device run for every new user who signs in, removing the previous multi-session SKU exception.
3 November 2026
Endpoints
Doc updateThe endpoint documentation now lists `mmcswdc01.blob.core.windows.net` and `mmcswdc02.blob.core.windows.net` for MEM-Win32Apps, alongside the existing hosts.
3 November 2026
Microsoft Configuration Manager
6 updatesEnable Tls 1 2 Server
Doc updateThe page now uses consistent .NET terminology and clearer instructions for framework support, security updates, and registry subkey updates by application and operating-system architecture.
2 November 2026
Admin Console
Doc updateThe article now states that the console is always installed on every site server and revises instructions for opening the console, connecting to a site, authentication, navigation, and PowerShell folder management. Screenshot descriptions were also updated.
2 November 2026
Enable Tls 1 2 Client
Doc updateThe documentation now more clearly separates the three client-enablement tasks, refines the sequencing for enabling TLS 1.2 and disabling older protocols, and updates .NET Framework wording and references.
2 November 2026
Index
Doc updateThe page date was updated to October 26, 2026, and the Download MDT link was removed.
2 November 2026
Tools
Doc updateThe page updates its date, rephrases guidance about the CD.Latest tools and supported Windows client operating systems, and standardizes punctuation, links, and code formatting.
2 November 2026
The overview was revised for clarity, including updated descriptions of co-management, workload piloting, licensing, Entra join terminology, and the relationship between co-management and Cloud Management Gateway (CMG). It now states that CMG and co-management are independent but can be used together.
2 November 2026