Axel GAULIARD 🇫🇷

The link below clearly illustrates the impact that many customers have confirmed. It should be given priority. techcommunity.microsoft.com/discussions/mi…

@IntuneSuppTeam, @AzureSupport, @AppleSupport, it would be amazing to work together to resolve an ongoing impact on iOS embedded Webkit not reporting correct device info to EntraID which breakes conditional access flows on any new enrolled iOS devices.

#PowerShell module IntuneWin32App has been updated to version 1.5.0 - Before you update, read the release notes here: github.com/MSEndpointMgr/…

@IntuneSuppTeam Hey, we are using Autopatch to manage the quality, feature, driver and Edge updates since weeks. Happy to see the new Autopatch reports with the 2602 Intune update. Is it a bug to see "0" devices in "Managed for quality updates" but in "Assigned to update rings"?

@IntuneSuppTeam Hey, thank you, we have already tested it and it works, but why is the date mentioned, which is supposed to work everywhere, still not working? We are in contact with Intune PM to look into this issue.

Hi, thanks for the info! If you're continuing to experience this issue, then you can resolve it immediately by renewing the license on the device using the following commands: - ClipDLS.exe removesubscription - ClipRenew.exe To the point regarding the issue being resolved by February 27th, as per our documentation here: msft.it/6016Q5JnO you are correct, and we’ll be reviewing this further. Thanks again for flagging this! ^IH

Did you notice that the Secure Boot policy that was previously showing the 65000 error suddenly started applying? The Secure Boot policy that was rejected by licensing was not fixed by a Windows update. Microsoft fixed the licensing logic service side. When a device refreshes its license by contacting licensing.mp.microsoft.com, typically every 30 days, the same policy can start working without any configuration changes. patchmypc.com/blog/intune-po… #Intune #MSIntune #Windows #Windows11

@IntuneSuppTeam, is there an approximative date to share about a future release of the latest Security Baseline for M365 Apps for enterprise v2512? This current version in Intune remains v2306 which is very old.... Thx!

@Mister_MDM The report seems again available 🎉

I guess this says it all... Secure Boot Report.... and it's gone... It seems the Secure Boot Report was pulled back for yet unknown reasons. (or maybe because the data in the report wasn't 100% accurate...) #Intune #MSIntune #Windows #Windows11 #WindowsUpdates #Autopatch

@IntuneSuppTeam Ah yeah, look in the Driver updates page, it's filtered correctly here, I'm sure it can be improved in all pages 👐

Hi Axel, 👋 Thanks for calling this out! The report is currently sorted alphabetically by name, which is why you're seeing that order. We understand how viewing rings in deployment sequence would be more intuitive. We'll be sure to share this feedback with the product team. Appreciate you raising it! 🙌 ^MM

Hey @IntuneSuppTeam , would it be possible to consider sorting correctly in Windows Autopatch "Reports | Windows Quality Updates"? The "Last" is at the top and the "Test" is at the bottom.. We all understand that it is sorted by name, but an effort would be helpful for all 🫶

Allow my organization to manage my device.... That single prompt has caused more unintended enrollments than most policies ever will. A user adds a work account, clicks the wrong button, and suddenly, the device is managed. Fun!!! For years, the only defense was telling users to click No and hoping they actually did (or blocking personal devices). Now there is real control over that behavior. This blog walks through what changed, how to disable automatic MDM enrollment during account registration, and what is happening behind the scenes before the option fully lands in the portal. With the feature now finally working, you may want to read the blog for all the details! patchmypc.com/blog/finally-c… #Intune #MSIntune #Windows #Windows11

@Mister_MDM @IntuneSuppTeam Grlll... thanks for the info! Between waiting for the licence recheck on my test devices so that the Intune policies work ‘as you explained’ and the withdrawal of this report, everything is fine and June is still coming, however :)

@AxelGauliard @IntuneSuppTeam They are aware :) .. they also updated the docs mentioning that is pulled back untill its fixed...

@IntuneSuppTeam, when the 2026.01 00B will be published to the Intune tenants? We are already 3 days after the publication of the update in the message center.

@IntuneSuppTeam admin.cloud.microsoft/?source=applau… Interesting message in the message center!

@AxelGauliard You certainly did. 🙂 We appreciate everything the community does to help us improve and address any potential gaps. Thanks, Axel! ^MM

@IntuneSuppTeam, Is it possible to get a clear state of the "Gradually" option in Intune for Feature update policy? Previously, there was a red warning: "Gradual rollout will no longer be an available option after Oct 14, 2025."

@IntuneSuppTeam, seems the doc have been updated 5 days ago, interesting 😇 The warning is no longer in the doc, and now shows a great explaination of the "Gradually" rollout option. Have I pointed the finger at something once again?😎

Our current strategy uses 12 rings to spread thousands of devices for feature updates because Gradually was expected to be deprecated. If it’s still available, we may simplify: fewer rings, using Gradually to split a ring into waves - that would be ideal! Thank you! ☃️