Rootly Tutorial
Doc updateThe guide now provides explicit Rootly fields for the Entra identifier, login and logout URLs, PEM certificate, and domain, followed by enabling and saving the SSO configuration.
Daily.Entra.NewsDaily AI-generated highlights from Microsoft Learn and Message Center. Browse the archive from 15 April 2025 → About this project →
The most consequential update concerns the transition away from Microsoft-provided SMS and voice authentication: Entra guidance names Soprano and Telesign as initial private-preview providers and says selection and configuration through Microsoft Security Store begins October 30, 2026. Other changes add Workload ID setup detail, clarify a save requirement for SAML certificate notifications, define PIM for Groups protection scope, and correct Rootly provisioning instructions.
The updated Entra authentication guidance identifies Soprano and Telesign as initial private-preview providers and states that provider selection and configuration through Microsoft Security Store begins October 30, 2026. It also frames passkeys as the default while Microsoft-provided SMS and voice authentication retire, directing affected administrators toward a provider or passkeys and another phishing-resistant method.
The setup guidance now covers both applications and user-assigned managed identities, using Microsoft Graph for applications and Azure Resource Manager for managed identities. It also documents credential properties including claimsMatchingExpression.
Administrators who configure notification email addresses through Microsoft Graph or PowerShell are instructed to re-confirm the address under SAML Certificates and select Save in the Microsoft Entra admin center. Without re-saving the SAML settings, certificate expiration notification emails might not be sent.
The updated guidance says credential protection for role-assignable groups covers members and owners, including eligible members and owners who have not yet activated their assignments.
The Rootly provisioning tutorial changes the Tenant URL from https://docs.rootly.com/integrations/scim to https://rootly.com/scim. Administrators configuring Rootly SCIM provisioning should use the new endpoint.
This period briefing was generated by AI from the tracked Microsoft Learn and Message Center changes.
The guide now provides explicit Rootly fields for the Entra identifier, login and logout URLs, PEM certificate, and domain, followed by enabling and saving the SSO configuration.
The tutorial now lists the Rootly fields to populate with the copied URLs and PEM certificate, then instructs administrators to enable and save required SSO. The previous instruction to send these details to Rootly support was removed.
Administrators configuring notification email addresses through Microsoft Graph or PowerShell should re-confirm the address under SAML Certificates and select Save in the Microsoft Entra admin center.
The article title no longer includes “(preview)” for custom call-outs using LCW extensibility workflows.
The documented Tenant URL changed from `https://docs.rootly.com/integrations/scim` to `https://rootly.com/scim`.
The tutorial now specifies `https://rootly.com/scim` as the Tenant URL instead of `https://docs.rootly.com/integrations/scim`.
The documentation identifies Soprano and Telesign as initial private-preview providers for SMS and voice authentication. It also states that provider selection and configuration through Microsoft Security Store will begin October 30, 2026.
The documentation now identifies Soprano and Telesign as initial providers and links to their commercial offers. Configuration begins October 30, 2026.
The documentation now states that credential protection covers group members and owners, including eligible members and owners who have not yet activated.
The role-assignable groups description now includes members and owners, including eligible members and owners who have not activated their assignments.
The documentation now explains setup for applications and user-assigned managed identities, using Microsoft Graph for applications and Azure Resource Manager for managed identities. It also adds details about credential properties, including claimsMatchingExpression.
The guidance now covers applications and user-assigned managed identities, including Azure Resource Manager setup instructions and updated GitLab claim-matching requirements.