Help Desk - Email "400 Bad Request" or "SAML assertion is not present in the token" Error

This document will describe how to fix the "SAML assertion is not present in the token" or "400 Bad Request" error when trying to access Outlook Email.

Note: If you have activated in the last 24 hours, please wait the full 24 hours and try again. If the error is still there after 24 hours, please contact the Help Desk. 

If you see see one of the following errors:
SAML assertion not present in the token error
When a user is attempting to log in to their UW-Madison email account for the first time, they may see a “SAML assertion is not present in the token” error. This can occur when they are trying to sign in to their email before activating their NetID services. 

400 Bad Request Error

When a user is attempting to log in to their UW-Madison email account after a lapse in affiliation, they may see a "400 Bad request" error. This can occur when their account was partially deactivated due to a lapse in affiliation, and was not fully reactivated upon their return.

Keywords:
SAML assertion is not present in the token activate services email outlook error m365 o365 netid microsoft365 office365 400 bad request 
Doc ID:
129450
Owned by:
Ara M. in Microsoft 365
Created:
2023-07-03
Updated:
2026-06-12
Sites:
DoIT Contract Partner Support Help Desk, DoIT Help Desk, Microsoft 365