Sign in with your existing Microsoft Entra ID (Azure AD) accounts
Also listed as: Azure AD & identity-platform integration
What is it?
Xelence connects to Microsoft Entra ID, formerly Azure AD, so staff can sign in with the accounts your organization already manages, including single sign-on (one sign-in for several systems).
Why does it matter?
Fewer separate passwords for staff, and user access managed in the directory your IT team already runs.
Start thinking about
- Which identity provider, such as Entra ID or Okta, should staff and constituents use to sign in?
- Which of your policies, such as password, session or network rules, should Xelence enforce?
- How often do you review user roles and access, and who signs off on the review?
- How quickly can you remove access when staff change roles or leave?
- What does your policy say about using generative AI with personal or sensitive information?
- How will you fit the security changes in each release into your change and testing process?
Terms used on this card
- Connector
- A ready-made link between Xelence and another system or service, such as Salesforce, DocuSign or an identity provider, so data flows without custom code.
- Microsoft Entra ID
- Microsoft's identity service, formerly called Azure Active Directory (Azure AD), which many organizations use to manage staff accounts and sign-in.
- Single sign-on (SSO)
- Signing in once with your organization's account to use several applications, such as through Microsoft Entra ID or Okta.