# Microsoft Authentication **URL:** https://meta.discourse.org/t/microsoft-authentication/51731 **Category:** Plugin **Tags:** official, auth-plugins, 365-oauth, included-in-core **Created:** [October 19, 2016, 10:28am UTC](https://meta.discourse.org/t/microsoft-authentication/51731 "2016-10-19T10:28:12Z") **Posts on this page:** 1 **Showing post:** 1
### Author: ![Discourse](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/discourse/32/148734_2.png) [@Discourse](https://meta.discourse.org/u/Discourse) #### Post date: [October 19, 2016, 10:28am UTC](https://meta.discourse.org/t/microsoft-authentication/51731/1 "2016-10-19T10:28:12Z")
> :discourse: Hosted by us? This plugin is available on our Business and Enterprise plans. [Amazon & Microsoft Logins | Discourse - Civilized Discussion](https://www.discourse.org/plugins/amazon-microsoft-login.html) | | | | | --- | --- | --- | | :discourse2: | **Summary** | Enable users to log in using their Microsoft accounts (aka Office 365 or Microsoft 365 accounts) | | 📖 | **Install Guide** | **This plugin is bundled with Discourse core**. There is no need to install the plugin separately. | > [@](#): > > :discourse2: As this is an #official plugin maintained by the Discourse team, #Support, #Contribute > Bug, #Contribute > UX, and #Contribute > Feature requests can be made in the respective categories here on Meta, and tagged with the appropriate plugin tag. Click on a link below to get one started. 👍 > > [❓  **Support**](https://meta.discourse.org/new-topic?category_id=6&body=%3E%20Before%20asking,%20did%20you%20search%20first%3F%20Press%20%F0%9F%94%8D%20at%20the%20upper%20right%20to%20search.&tags=365-oauth "Ask for support on configuring and using Microsoft Authentication") [🐛  **Bug**](https://meta.discourse.org/new-topic?category_id=1&tags=365-oauth "A bug report means something is broken, preventing normal/typical use of the plugin") [👀  **UX**](https://meta.discourse.org/new-topic?category_id=9&tags=365-oauth "Discussion about the user interface of Microsoft Authentication") [💡  **Feature**](https://meta.discourse.org/new-topic?category_id=2&tags=365-oauth "Discussion about how existing Microsoft Authentication features can be improved or enhanced, and how proposed new features could work") ## Summary Microsoft Authentication enables users to log in to your Discourse forum using their Microsoft accounts (also known as Office 365 or Microsoft 365 accounts). This simplifies the login process for organizations that use Microsoft services. ![Microsoft auth login screen](https://global.discourse-cdn.com/meta/original/3X/d/4/d4adf96604993d2a6e9398b5082c971dd0dcab6a.png) ## Features - Allows users to log in with their Microsoft credentials - Supports both multi-tenant and single-tenant configurations - Integrates with Microsoft Azure Active Directory - Simplifies user registration and login ## Configuration To set up Microsoft Authentication for your Discourse forum: 1. Visit [Azure Portal’s App Registration page](https://portal.azure.com/#blade/Microsoft_AAD_RegisteredApps/ApplicationsListBlade) 2. Register a new application: 3. Add your site as a Redirect URI for Web in this format: 4. Save your changes 5. Visit **Certificates & secrets** in the left sidebar menu and click **New client secret** 6. Visit **Overview** (in the left sidebar) and copy the Application (client ID) 7. In your Discourse admin area, go to Settings and search for “microsoft auth” 8. Enter the Application ID and Secret from the previous steps ## Single-tenant authentication issues If you’ve configured your Microsoft application as `single_tenant`, some users may experience issues when logging in. This happens because the emails used for login are considered untrusted, and the system cannot automatically link them to existing Discourse accounts. To resolve this issue, users can: 1. Look for the “Already have an account?” section at the bottom of the signup form 2. Click the provided link to go through the account link-up process 3. Complete the authentication steps to connect their Microsoft account to their existing Discourse account Another option is to enable the `microsoft auth email verified` site setting, if admins are confident that all your users have verified emails.This ensures that returning users with existing accounts don’t create duplicate accounts when authenticating through Microsoft. ## Additional configuration options You can update all Microsoft Authentication settings by visiting the Admin \> Settings area and searching for “microsoft auth”. For single-tenant setups, you’ll need your tenant ID, which you can find in the [Azure Portal tenant properties](https://portal.azure.com/#view/Microsoft_AAD_IAM/TenantProperties.ReactView). ## Additional resources - [Potential account take over due to unverified emails from Microsoft Identity Platform · Advisory · discourse/discourse-microsoft-auth · GitHub](https://github.com/discourse/discourse-microsoft-auth/security/advisories/GHSA-2w32-w539-3m7r) > Last edited by @tobiaseigen 2025-07-16T21:37:09Z > > > **Check document** > > > > Perform check on document: --- _[View the full topic](https://meta.discourse.org/t/microsoft-authentication/51731)._