Hey Jeremy,
Email fetching with M365 is core osTicket functionality, so it’s definitely in our wheelhouse even though it’s not osTicket Awesome-specific.
The good news: this isn’t a product issue. M365 email fetching works reliably once it’s set up. The complexity is entirely on the Azure side, where Microsoft requires OAuth2 authentication and the app registration process has a few spots where a missed setting can silently block things. It’s a one-time configuration, though. Once the OAuth2 handshake is done, it just runs.
A couple of quick questions so I can point you in the right direction:
What version of osTicket Awesome are you running?
Where are you getting stuck? Specific error message, or is the fetch just silently not pulling mail?
If you haven’t seen it already, the official walkthrough covers the Azure app registration and osTicket configuration end to end: Microsoft Authorization Guide
The things that trip people up most often are Azure API permissions missing admin consent, authenticating as the wrong M365 account during the OAuth flow, and the callback URL not matching exactly. All straightforward fixes once you know where to look.