Skip to main content
Getting Started Last updated: 6 March 2026

How to Verify Your Outlook Connection

Check your authentication status, re-authenticate after token expiry, and confirm which account is connected.

Check whether Outlook Assistant is authenticated, see which account is connected, and re-authenticate when tokens expire.

Check Authentication Status

Ask your AI assistant:

“Check my Outlook auth status”

The auth tool is called:

tool: auth
params:
  action: status

A healthy response shows:

  • Authenticated: Yes
  • Account: your-email@outlook.com
  • Token expires: date and time
  • Scopes: the permissions granted

If the token has expired, the tool will report it and suggest re-authenticating.

Auth tool status output showing authenticated user

Re-authenticate After Token Expiry

Tokens expire periodically (typically after 1 hour, with automatic refresh). If refresh fails, re-authenticate:

  1. Start the auth server:
npx @littlebearapps/outlook-assistant auth-server
  1. Ask your AI assistant:

“Re-authenticate my Outlook account”

tool: auth
params:
  action: authenticate
  force: true

The force: true parameter bypasses the existing (expired) token and starts a fresh OAuth flow.

  1. Open the URL, sign in, and grant permissions as before.

Check Server Information

To see the server version and capabilities:

“Show Outlook Assistant server info”

tool: auth
params:
  action: about

This returns the server version, available tools, and configuration details.

Common Connection Problems

SymptomCauseFix
”Not authenticated”No token file existsRun through the initial setup
”Token expired” with auto-refresh failureRefresh token revoked or client secret changedRe-authenticate with force: true
Auth succeeds but API calls fail with 403Insufficient permissionsAdd missing permissions in Azure Portal, then delete ~/.outlook-assistant-tokens.json and re-authenticate to pick up new scopes
”AADSTS700082”Refresh token expired (>90 days inactive)Re-authenticate with force: true
”AADSTS7000215”Client secret is wrong (using Secret ID instead of Value) or has expiredCheck Azure Setup Guide — Client Secret
”Need admin approval” during OAuthOrganisation requires admin consentAsk your IT admin to grant consent — see Admin Consent
Token file exists but auth reports failureCorrupted token fileDelete ~/.outlook-assistant-tokens.json and re-authenticate
Auth server says “missing client ID”Auth server does not have env varsCreate a .env file or export OUTLOOK_CLIENT_ID/OUTLOOK_CLIENT_SECRET in your shell — see Connect guide
search-emails returns no resultsPersonal account $search limitationUse subject, from, to, receivedAfter filters instead of query — see Known Limitations

Tips

  • Tokens auto-refresh in the background — you rarely need to manually re-authenticate
  • If you switch Microsoft accounts, use force: true to authenticate with the new account
  • The token file at ~/.outlook-assistant-tokens.json contains sensitive credentials — don’t share or commit it

Frequently Asked Questions

How often do I need to re-authenticate?

Rarely. Access tokens expire after about 1 hour, but the MCP server automatically refreshes them using the refresh token stored in ~/.outlook-assistant-tokens.json. Refresh tokens last up to 90 days of inactivity. You only need to manually re-authenticate if:

  • You have not used Outlook Assistant for more than 90 days
  • You changed your Microsoft account password
  • Your client secret expired (check the expiration date in Azure Portal)
  • An admin revoked your app’s consent

Can I use Outlook Assistant on multiple computers?

Yes, but each computer needs its own authentication. The token file (~/.outlook-assistant-tokens.json) is stored locally and is not shared between machines. Run through the authentication steps on each computer.

Your Azure app registration and client credentials (OUTLOOK_CLIENT_ID/OUTLOOK_CLIENT_SECRET) are the same across all computers — only the token file differs.

What is the auth server and do I need it running all the time?

No. The auth server (port 3333) is only needed during the OAuth login flow. Once you have authenticated and tokens are saved, you can stop it. See Understanding the Two Processes for details.

My client secret is expiring soon — how do I rotate it?

See When Your Secret Expires in the Azure Setup Guide.

Was this helpful?

Related Articles