September release - Full pipeline visibility, automatic retries and smoke tests on W365 Cloud PCs

Five areas carry this release: sequences now retry themselves after a transient failure, the pipeline a package went through is now visually exposed, Task Runner provisioning is faster, smoke tests can run on Cloud PCs the customer already owns, and the Deployment Health Check now runs 44 rules where it ran 22, and can be run on demand. 🔁 Automatic retry for failed sequences Sequences that fail with a known temporary error now retry themselves from the step that failed. No one has to press retry. It's on by default. It retries up to 3 times, waiting 5, then 15, then 45 minutes between attempts. You can configure all of it on the Sequence Retry settings page: which error messages count as retry-able how many retries (up to 10) the first delay, and whether the wait grows with each attempt A built-in preview shows exactly when each retry will run. Every automatic retry is recorded in the package's Pipeline History. Changes apply to future sequence runs; sequences already running aren't affected. Each retry runs as its own separate sequence, marked with the time it was retried — so you always have a clear record of every attempt and when it happened. 🧭 Package pipeline history & manual retry Open any onboarded application's details page to see the full pipeline its package went through, drawn as a visual graph. From there you can also take action: retry a single sequence, or restart the whole pipeline from any step you choose. You'll see the full history of each sequence too, with a direct link to open the sequence itself. ⚡ Faster, clearer Task Runner provisioning Preparing a Task Runner now takes less time. When it fails, it names the actual cause, such as an unreachable key vault, a missing secret or a domain join failure. Problems that used to look like a silent stall now show up as a clear error. ☁️ Smoke tests on your own Windows 365 Cloud PCs Already have a Windows 365 estate? Link your existing Cloud PCs with the Link Cloud PCs wizard and run smoke tests on them. On linked Cloud PCs the platform only has read-only permissions, and unlinking a Cloud PC removes only our record of it. Linked Cloud PCs run smoke tests in Persistent mode. 🩺 Deployment Health Check 1.1.0 The health check now runs 44 rules instead of 22. It goes deeper on identity and permissions, networking, storage and key vault access, and connectivity to Microsoft services. You can re-run it whenever you like, and the report shows the evidence behind every result. 🐞 Bug fixes & enhancements Detection rules now support the full set of Intune value types across registry, file, product code and script rules. Detection rules imported from SCCM can now be edited. When several registry detection rules are found for an application, the correct one is now chosen. We've introduced filtering inside Sequences page: now sequences can be filtered by creation date and status.