I'm struggling with the Company Portal. What is the correct way to roll out that app during Autopilot? Right now, it seems to be throwing errors that break my enrollment (just the generic errors about an app failed to install) and while it's a given I'm doing something wrong, I'm wondering how to rectify it.
https://techcommunity.microsoft.com/event/windowsevents/windows-office-hours-july-16-2026/4529243
"If you are an IT admin with questions about managing and updating Windows, we want to help. Every third Thursday of the month, we host a live chat-based event on the Tech Community called Windows Office Hours. Members of the Windows, Microsoft Intune, Windows Autopilot, Windows Autopatch, and Windows 365 engineering teams will be standing by to answer your questions.
Want to attend the July 16 session of Office Hours? Add it to your calendar and select Attend on the event page to let us know you're coming. There is no video or live meeting component. Simply visit the event page, sign in to the Tech Community, and leave your questions in the Comments section. You can also bookmark https://aka.ms/Windows/OfficeHours for upcoming dates (and the ability to add this event to your calendar). We look forward to helping you."
I came across this article about the deprecating of CBA for Exchange ActiveSync. We are impacted, but I can't figure out what do to about it. All the article says is "his may involve updating the device's email profile or MDM/Intune device configuration profiles.".
This is incredibly vague. Does anyone know what changes actually need to be made? We already have Entra CBA set up but I can't see how to have Intune tell our phones to start using it.
Just wanted to know how IT admins have had any downloads issues when using edge , where downloads will hang then shortly finish. I am not sure if this is a pua issue or smart screen or maybe both . Would love any feedback
When you put all the changes that Intune engineering has made next to each other, it starts to look like something much bigger than a few simple latency improvements.
Intune is slowly moving away from waiting for timers and scheduled polling, toward push, local events and near real time actions.
Policy delivery: The old roughly 30-minute notification throttle is being replaced by the Fast Lane model. Changes can trigger a new device check-in within minutes instead of sitting behind the old notification window.
Remote actions :That annoying 5-minute queued delay after the first hours of enrollment? Gone on supported Windows versions. Remote actions can start the device check in immediately again.
Device Sync: Sync used to mainly wake the Windows MDM world. Now one Sync can wake Windows MDM AND the Intune Management Extension. The IME side is delivered through IC3 and Trouter.
Sync Status :It is no longer just “press Sync and hope”. The portal can now follow the progress of Policies, Applications, and Scripts.
Win32 apps: A newly assigned Required Win32 app no longer necessarily has to wait for the normal 60-minute app check. Intune can push intent 2 over IC3 and bring the normal app check forward within minutes.
Autopilot apps: When enrollment finishes, it can now trigger a fresh app check. That closes the gap where the desktop appeared, but the remaining Required apps could sit there waiting for the next app timer.
Client-driven compliance: This one is even more interesting. The device can watch local signals such as Firewall, Defender, BitLocker, Secure Boot, and TPM. When something changes, it can proactively request a new compliance evaluation instead of waiting for the normal cycle.
App Inventory: This used to be based around a 4-hour collection cycle. The newer Device Inventory Agent can react to an application change, validate it, and upload the delta on the next scheduler pass. In my testing, that was about 5 minutes.
So...
Do you still think Intune is slow?
I think that question is becoming a lot harder to answer with a simple “yes”.
Of course the whole reporting backend is another story… ao hopefully that part is up next
Interactive study aid for Microsoft Intune and Microsoft Entra ID
You work through support tickets, inspect the evidence and decide what to do next. Each answer review explains the correct response and includes a Microsoft Learn reference.
The Intune scenarios include device compliance, Win32 app detection and Windows update recovery. The Entra ID scenarios cover Conditional Access, authentication strengths, PIM activation and Temporary Access Pass.
Some tickets bring the two together. For example, successful MFA doesn’t necessarily explain why an application is still blocked. You need to check the policy requirements, device status and stated local procedure before choosing a response.
Hosted it on my website: controlaltdeletetechbits.co.uk. Select the Tenant Defender desktop icon to try it.