Hi. Are there any plans to improved the functionality of the Multi Admin Approval (MAA) polices in Intune. Given some recent high profile wiper attacks MAA is more important than ever to configure. At the moment there are no prompts when an Intune admin requests to wipe a device. They literally have to manually contact the approvers and say 'hey, can you approve that wipe request'. Also an MAA policy that would require MAA approval for an Autopilot reset currently does not exist. An bulk Autopilot reset can do as much damage as a bulk device wipe request. Thanks. 

Where can we find the Autopatch report endpoints in Graph?

It looks like W365 has priority to resolve conflicts? Intune admins have been asking for that for years (since migrating from Group Policy). Will that be coming to workstations?

Good to see you all again. I used to see during the bi-monthly engineering meetings.

Currently there is a nice preview feature to run remediation scripts manually on individual devices.
Is there a way to run a remediation script manually to a number of devices, like a bulk action.

Just in case there isn't currently :)
https://feedbackportal.microsoft.com/feedback/idea/22a47388-cf26-f111-9730-0022485314bc

p.s. Thanks for the sessions, they are great.

Welcome to “Unpacking Endpoint Management: Live from Tech Takeoff 2026” at Microsoft Technical Takeoff. Q&A is open now and throughout the week. Please post any questions or feedback here in the Comments. [Note: If your organization’s policies prevent you from seeing the video on this page, you can also tune in on LinkedIn.]

If a user who enrolled a device is deleted (eg, could be user from stale enrolment package) for whatever reason, the device then becomes eternally non-compliant because "User exists" will always be False. (thinking mostly about shared devices in a classroom)

What is the most efficient way to deal with this without having to reimage the device.

We’re actively transitioning from on‑prem Group Policy to Intune configuration profiles as our primary configuration model.
In Group Policy, we relied heavily on hierarchy, inheritance, and layered targeting to manage complex and evolving scenarios at scale.

From a product and engineering perspective, what are the best practices for designing Intune configuration profiles upfront—around scoping, modularity, and ownership—to minimize long‑term technical debt when new or unexpected scenarios emerge after hundreds of profiles are already in production?