Tech Trends and Insights

Microsoft Intune MAA Connectivity Validation Guide 🔐 Microsoft Intune MAA Connectivity Validation Guide This guide provides a practical method for validating network connectivity from a Windows 11 endpoint to the Microsoft Azure Attestation (MAA) endpoints used by Microsoft Intune. The objective is to determine whether DNS resolution, TCP 443 connectivity, HTTPS communication, proxy configuration and possible TLS inspection issues could prevent the endpoint from reaching the required MAA service. Executive Summary This guide validates the network path to the Microsoft Azure Attestation service. It is designed to help administrators distinguish a connectivity problem from a device health, Intune policy or compliance configuration problem. A successful test confirms that the tested endpoint can reach the MAA service over HTTPS. It does not by itself prove that a Windows Health Attestation session or Intune compliance evaluation has successfully comple...

  Microsoft recently introduced Remote Help Unattended Support with Remote Sign-In , allowing IT administrators and helpdesk staff to remotely access Intune-managed Windows devices without requiring an end user to be present. This guide documents a complete lab-tested deployment , including setup, configuration, troubleshooting, and lessons learned during real-world testing. Disclaimer This guide is based on a manual proof-of-concept deployment . For production environments, Microsoft recommends deploying the required Azure Virtual Desktop components through Intune as Win32 applications. What is Remote Help Unattended Support? Traditional Remote Help requires a signed-in user to approve the support session. With Unattended Support with Remote Sign-In , administrators can: Connect to a managed Windows device when no user is present Sign in using their own credentials Work in a separate Windows session Perform maintenance after business hours Support kiosk devices, public computers, ...

Introduction Microsoft recently introduced the ability to collect Windows Registry data using Device Inventory and the Properties Catalog in Intune. While most examples focus on application inventory and configuration validation, I wanted to explore a different use case. Many security-related events leave traces in the Windows registry. For example, enabling Remote Desktop, configuring a proxy server, or installing remote access software often results in registry changes that can be monitored. Traditionally, identifying these changes required PowerShell scripts, remote access tools, or dedicated security products. With Registry Inventory, administrators can collect selected security-related registry values directly from managed devices and review them centrally in Intune. This provides an additional layer of visibility without connecting to the endpoint. Why This Matters Security teams are often asked questions such as: Has Remote Desktop been enabled on any devices? Are users configur...

Introduction Microsoft recently introduced the ability to collect Windows Registry data using Device Inventory and the Properties Catalog in Intune. While most examples focus on application-specific registry data, I wanted to explore a practical use case for Windows kiosk devices. In environments such as libraries, schools, and public-access workstations, kiosk devices often rely on specific registry settings for automatic sign-in and user experience configuration. When these settings change unexpectedly, troubleshooting can become time-consuming and often requires remote access, PowerShell scripts, or manual registry inspections. With Registry Inventory, administrators can now verify these settings directly from Intune and gain visibility into device configurations without connecting to the endpoint. Why This Matters One of the most common support issues for kiosk devices is that: Automatic sign-in stops working The wrong local account is configured A device is rebuilt incorrectly Reg...

With recent changes introduced for users in the European Economic Area (EEA), Windows 11 users may see an additional consent prompt when Microsoft apps attempt to use the account already signed in to Windows. For managed environments, this extra prompt can create unnecessary user interaction. Microsoft has introduced a new policy that allows administrators to automatically approve this permission on supported devices. In this post, I'll show you how to deploy this configuration using Microsoft Intune Remediations. 📌 Prerequisites Before you begin, make sure the following requirements are met: Windows 11 version 24H2 or later July 2026 security update installed (KB5101650 or later) Device enrolled and managed by Microsoft Intune User signed in with a Microsoft Entra ID account Microsoft Intune Remediations license 📦 Deployment Options There are several ways to deploy this configuration across Windows devices: Group Policy (GPO) – Suitable f...

If you’re still using Quick Assist in enterprise environments, it’s time to move forward. With Remote Help in Intune , you get: ✅ Entra ID integration ✅ Role-based access control (RBAC) ✅ Elevation support ✅ Auditing and logging 🔔 Important: Starting June 2026, Remote Help is included in Microsoft 365 E3 and E5 licenses — removing the need for separate licensing and making it the natural choice for enterprise remote support. 🔐 Step 1 – Assign Required Roles (Important!) Before anything else, you must assign the correct roles. Navigate to: Intune admin center → Tenant administration → Roles ✅ Recommended roles: Help Desk Operator Remote Help Operator (if available in your tenant) Required permissions: Remote Help usage Device interaction User support capabilities 👉 Without proper role assignment, Remote Help will either fail or run in limited mode. Step 2 – Enable and Configure Remote Help Go to: Intune admin center → Tenant administration → Remote Help Enable the following: ✅ En...