Keep authentication in one place
Azure AD remains the system that decides who is authenticated. Xoxoday relies on it over SAML 2.0 rather than holding its own passwords for your workforce.
Azure ADSign in to Xoxoday with
Sign in to Xoxoday with
Azure AD single sign-on
Let employees reach recognition and rewards with the Azure AD identity they already use.
Book a demo
Get a personalised walkthrough. We respond within one business day.
What you can do
Four things you get once Azure AD is connected
Azure AD handles identity. Xoxoday relies on it, so access to rewards follows the controls your IT team already runs.
One login, no new passwords
- Sign in with the Azure AD identity people already have
- Employees reach Xoxoday through Azure AD over SAML 2.0. No separate Xoxoday credentials to create, remember, or reset.
- Authentication stays in Azure AD
- Your Azure AD sign-in policies stay in charge of who gets in, so access follows the controls your IT team already runs.
Access managed centrally
- Provision and deprovision in Azure AD
- Access is managed entirely through Azure AD. Your admin adds and removes users in the portal they already use.
- One-way, from Azure AD to Xoxoday
- Identity decisions flow from Azure AD to Xoxoday, keeping ownership with your IT and security team.
Matched to the right profile
- Name ID by email or employee ID
- The Name ID must match the Email ID or Employee ID in the Xoxoday user records so each person lands on their own profile.
- Metadata upload or manual entry
- Upload the Azure Federation Metadata XML to Xoxoday, or enter the values by hand. Optional Relay State and Logout URL are supported.
Test before you switch
- Test the connection from Xoxoday
- Run a connection test from the Xoxoday admin interface before anyone depends on it for sign-in.
- Separate from Microsoft OAuth
- Azure AD SAML SSO is its own option, distinct from the built-in Microsoft OAuth sign-in.
Use cases
Who runs it, and what for
Three ways teams use Azure AD with Xoxoday.
Reach recognition and rewards without friction
Employees open Xoxoday with the Azure AD identity they use every day, so recognition and reward programs are one sign-in away.
Remove access where you manage it
Provision and deprovision users centrally in Azure AD, and Xoxoday access follows without a second admin console to maintain.
How it works
From Azure app to employee sign-in
Step 1
Add Xoxoday in Azure
In the Azure portal, add Xoxoday as a non-gallery enterprise application.
Step 2
Enter Xoxoday values in Azure
Copy the Xoxoday service provider values, such as Entity ID and ACS URL, into the Azure SAML configuration.
Step 3
Upload Azure metadata
Download the Federation Metadata XML from Azure and upload it to Xoxoday.
Step 4
Test the connection
Run the connection test from the Xoxoday interface to confirm sign-in works.
Setup
SAML 2.0 setup, step by step
Exchange metadata between Azure AD and Xoxoday, then test the connection.
Native Azure AD SSO over SAML 2.0, available across Empuls, Plum, and Loyalife.
One-way, from Azure AD to Xoxoday. Users are provisioned and deprovisioned centrally in Azure AD.
Entity ID, ACS URL, SSO redirect URL, and a Name ID matching Email ID or Employee ID. Relay State and Logout URL are optional.
Azure portal admin access and Super Admin access to Xoxoday.
Common Questions
Frequently asked questions
Common questions from IT, security, and HR admins evaluating Azure AD SSO for Xoxoday.
Still have a question? Talk to usSAML 2.0.
Through the Name ID, which must match the Email ID or Employee ID in the Xoxoday user records.
Admin access to the Azure portal and Super Admin access to Xoxoday.
One-way, from Azure AD to Xoxoday. You provision and deprovision users centrally in Azure AD.
Azure AD SAML SSO is a separate option from the built-in Microsoft OAuth sign-in, and is configured through an enterprise application in Azure.
Empuls, Plum, and Loyalife are listed for this integration. The step-by-step guide in the help center covers Empuls.
See it in your own Azure AD setup
A 30-minute call. We'll walk through the SAML 2.0 setup and how rollout to your teams would work.
Book a demo