The M365 integration does not work very nicely with enforced SSO using Azure AD as the IdP. If you have to log into Huntress.io using Azure AD SSO, then following the instructions in the M365 integration setup guide telling you to login to Huntress using an incognito window and then hitting the re-authorise button are redundant, because although you’ve used an incognito window, you’ve then had to immediately auth to a different Azure AD identity (not the Huntress Service Account), which renders the incognito window useless - it's no loger free of MS cookies. We ended up having to temporarily disable enforced SSO (which then annoyingly made everyone have to enrol MFA again), login to Huntress with direct credentials in an incognito window, then re-auth with the Huntress Service Account (twice, as per the docs). The alternative work-around is to make the Huntress M365 service account a Huntress portal admin so that you can login to the Huntress portal with that same account (via SAML SSO).