Microsoft Azure Single Sign On Setup

Microsoft SSO allows organizations that use Office 365 to login to the Edlio CMS using those same accounts.

Simplicity and Security. Reducing the number of passwords a user has and the number of locations in which a user is managed simplifies the entire administration. Microsoft's account security is quite good. Their two-factor authentication, password reset flows, and intrusion detection systems are impressive.
​
How SSO strengthens your CMS security

Single sign-on doesn't just make logging in easier — it adds meaningful security layers to your Edlio dashboard. Here's what changes when your district enables Microsoft SSO:

Your identity provider handles authentication, not Edlio. When SSO is active, Edlio never stores or manages user passwords. Authentication happens entirely through Microsoft, which means your users benefit from the enterprise-grade protections those platforms already provide — including two-factor authentication, suspicious-login detection, and automated password reset flows.

​Fewer passwords means fewer vulnerabilities. Every standalone password is a potential point of failure. SSO eliminates the need for a separate Edlio-specific password, so there's one less credential that can be forgotten, reused across sites, or compromised in a breach.

​User access stays in sync with your directory. Because SSO ties CMS sign-in to your existing Microsoft Entra ID accounts, user access follows your directory management. When a staff member leaves and their account is deactivated, their CMS access ends automatically — no separate cleanup in Edlio required.

​You can restrict sign-in to a specific Organizational Unit. Districts that share a single directory across staff and students can lock CMS access down to a designated staff OU, preventing students or other directory users from reaching the editing tools. See Restrict CMS Sign-In to an Organizational Unit for setup details.

​Your IT team keeps centralized control. Password policies, session rules, MFA requirements, and account deactivation are all managed in one place — your Google or Microsoft admin console — rather than split across multiple platforms.

1. Azure Active Directory (Azure AD)

To use Microsoft SSO to log into the Edlio CMS, your organization first needs Azure Active Directory.

If your organization does not already have Azure AD then follow these instructions:

Create an Active Directory on Windows Azure

2. Azure AD Application

Once you have Azure AD set up then you'll need to create an Azure AD Application:

Create Azure AD Application

For Microsoft's Legacy version of Azure, use these instructions: Create Azure AD Application (2017)