Staff at the Versailles Academy who try to add their professional address in Outlook or Gmail often encounter a connection refusal. The password is correct, the address is too, but the email client rejects the attempt. The main reason lies in the academy’s gradual transition to Microsoft 365 and the abandonment of simple password authentication in favor of the OAuth2 protocol.
Why the OAuth2 protocol blocks traditional IMAP configuration
The Versailles Academy now hosts its mailboxes on Exchange Online, the email component of Microsoft 365. This change has a direct consequence on how third-party software connects to the server.
With the old system, it was enough to enter the address, password, and IMAP/SMTP settings for synchronization to work. Exchange Online now requires an OAuth2 token instead of a password. Specifically, the application must open a Microsoft web window where the user identifies themselves, then retrieve a temporary authorization token.
Simply entering credentials in the IMAP fields of an email client is no longer sufficient. The error displayed resembles a password issue, but it is actually a rejection related to modern authentication. Multi-factor validation, if enabled by the rectorate, adds an additional step that only the OAuth2 flow can handle.
Before starting any configuration, it is essential to identify whether the concerned account has already switched to Microsoft 365. A reliable clue: if the ac-versailles webmail redirects to an Outlook Web App (OWA) interface, the migration is effective. It is possible to configure the Versailles email on Outlook by following the protocol suited to this new infrastructure.
Versailles Email on Outlook: Exchange Connection vs. IMAP Configuration
In Outlook (desktop version or mobile app), two configuration paths coexist, and choosing the right path determines the success of the operation.
Direct Exchange Connection
This is the recommended method for a Microsoft 365 account. By adding the account with the “Microsoft 365” or “Exchange” option, Outlook automatically manages OAuth2 authentication. The user enters their academic address, a Microsoft window opens, and the connection is established after validation.
- Synchronization covers calendar, contacts, and emails in a single operation, without manual server configuration.
- Server-side folders (drafts, sent, trash) appear as they are in the client, without naming discrepancies.
- Multi-factor validation is natively supported by this connection method, preventing recurring blocks.
This method works with Outlook for Windows, macOS, and the mobile Outlook app on iOS and Android.
Manual IMAP Configuration
IMAP configuration remains technically possible, but its reliability depends on the security policy applied by the academy at the time of the attempt. If basic authentication is disabled on the Exchange Online server, the IMAP connection via password will be refused without an explicit error message.
The usual server settings of the academy (IMAP incoming server, SMTP outgoing server, ports, and SSL/TLS encryption) remain the same. The problem does not come from these settings, but from the authentication layer that supersedes them.
Academic Address Versailles in Gmail: Concrete Limitations
Gmail offers to import external accounts via IMAP, in the “Accounts and Import” section of the settings. For an ac-versailles account migrated to Microsoft 365, this feature encounters a structural obstacle.
Gmail does not support OAuth2 authentication for third-party Microsoft accounts. The account addition form requests an IMAP server, an identifier, and a password. If the Exchange server refuses basic authentication, the connection systematically fails.
Two alternatives exist, each with its constraints:
- Use the Outlook application (desktop or mobile) as the primary client and check Gmail separately. This separation avoids authentication conflicts.
- Set up a redirection from the ac-versailles webmail to the Gmail address, if this option is still available. Field reports vary on this point: some staff report that automatic redirections have been disabled after the Microsoft 365 migration.
- Access the Outlook web interface (outlook.office.com) directly in the browser, which completely bypasses the need for an email client.
Missing Folders and Partial Synchronization After Configuration
Even when the connection is successful, a frequent problem persists: some folders do not appear in the email client. This phenomenon has a precise technical explanation.
Gmail and Outlook do not manage folders in the same way during an IMAP connection. Gmail uses a labeling system (“All Mail”, “Sent Mail”, “Trash”) that are actually views, not folders in the strict sense. These labels must be explicitly exposed to IMAP in the Gmail settings to appear in a third-party client.
Conversely, when connecting an ac-versailles mailbox in Outlook via IMAP, the Exchange server folders display according to their internal name. The “Sent Items” folder may appear under an English name (“Sent Items”), or may not sync at all if the automatic mapping fails.
The solution involves a manual check: in the IMAP account settings on the client side, each local folder (sent, drafts, trash) must be associated with the corresponding folder on the server. In the Outlook desktop app, this option is found in the account properties, under the “Folders” tab.
The transition of the Versailles Academy to Microsoft 365 has made manual configuration significantly less predictable than before. Prioritizing the Exchange connection in Outlook remains the most stable method. For Gmail, the lack of OAuth2 support for external Microsoft accounts constitutes a technical limitation that is neither dependent on the user nor the academy.
