TopicMicrosoft 365 →
⌚ About 2 min read
Auto SQL is often at the heart of Outlook or d profile creation problems, old Exchange environments.
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 the web.
Check that the box works in the browser.
-
2
Control DNS
Check the expected Auto-Divrective records.
-
3
Test the client.
Use the appropriate Outlook diagnostics.
-
4
Search for heritage.
Find old SCP or DNS URLs.
À retenir
- Avoid changing several methods of discovery at once.
- Store the results before change.
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.