TopicActive Directory →
⌚ About 2 min read
A short method allows to distinguish add-in, local profile and Microsoft 365 problem.
Avant de commencer : adaptez toujours les commandes et manipulations à votre environnement. Sur un système de production, prévoyez une backup ou un retour arrière lorsque l’action peut modifier la configuration.
Étapes à suivre
-
1
Test Outlook Web
- I'll take you to the box.
-
2
Run in Safe Mode.
Spread the supplements.
-
3
Test a new profile.
Do not delete the old immediately.
-
4
Control Auto-Divd.
If the test profile fails as well.
Commands utiles
Outlook.exe / Safe
À retenir
- Save the specific settings before re-create a profile.
- A global M365 incident may make local troubleshooting unnecessary.
Outlook / Autodiscover: identify the configuration source actually used
Technical checkpoints
- Autodiscover can use AD SCP, DNS, HTTPS redirects and Microsoft 365 services depending on scenario; a stale on-prem endpoint can remain influential in some environments.
- Outlook stuck loading a profile can come from profile/MAPI, OST, add-ins or authentication, not only Autodiscover.
- Tests should keep the URL and result of each step to avoid fixing the wrong Autodiscover source.
Client diagnosis
Test Autodiscover first, then create a fresh profile only if network/configuration is healthy.
Test-OutlookWebServices / Microsoft Remote Connectivity Analyzer
Outlook /safeTopic-specific pitfalls
- Removing an SCP or DNS record without an inventory can break remaining on-prem/hybrid clients.
- Deleting OST before ruling out a server-side problem can trigger unnecessary heavy resynchronization.
How to validate
- The client retrieves expected endpoints and authentication succeeds without stale URLs.
- A representative profile opens the mailbox and remains stable after restart.