Autenticação Microsoft

[Discourse]

Hosted by us? This plugin is available on our Business and Enterprise plans. Amazon & Microsoft Logins | Discourse - Civilized Discussion

	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.

As this is an official plugin maintained by the Discourse team, Support, Bug, UX, and 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  Bug  UX  Feature

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.

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

2. Register a new application:

   • Choose a name (typically your site name)
   • Under “Supported account types,” select the most permissive option for your needs
   

3. Add your site as a Redirect URI for Web in this format:

   • https://your.discourse.forum/auth/microsoft_office365/callback
   

4. Save your changes

5. Visit Certificates & secrets in the left sidebar menu and click New client secret

   • Add a simple description
   • Choose 24 months under “Expires” (note: you’ll need to renew it)
   • Copy the Value (this is the Application Secret) and save it for your plugin settings

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.

Additional resources

• Potential account take over due to unverified emails from Microsoft Identity Platform · Advisory · discourse/discourse-microsoft-auth · GitHub

Last edited by @tobiaseigen 2025-07-16T21:37:09Z

Check document

Perform check on document:

[시온_강]

I'm trying to use microsoft oauth, but I'm having a problem

Since I am trying to build a discourse for internal use, I chose this organizational directory only. However, the article Microsoft Authentication talks about setting up multi-tenant. [image] An error page is displayed as above. Could the Supported account types setting be the problem? I currently don’t have an MPN ID, so I can’t try setting up multi-tenant.

Estou tendo problemas para usar esse plugin.
Você poderia me dar algum conselho?

[nathank (Nathan Kershaw)]

Como já me confundi (novamente) ao atualizar minha configuração para este plugin, fiz este PR:

Improve documentation and setting description

O problema é que o painel do aplicativo Microsoft oferece três campos com aparência provável para o ‘Segredo’ - Client ID Value e ‘Secret ID’. Sem orientação, escolhi o errado em ambas as ocasiões em que lidei com isso, e suspeito que não estou sozinho!

[moggleif (Morgan Johansson)]

Acabei de testar este plugin e ele não funciona para tenant único.

Por quê?

lib/omniauth-microsoft365.rb

option :client_options,
             site: "https://login.microsoftonline.com",
             authorize_url: "/common/oauth2/v2.0/authorize",
             token_url: "/common/oauth2/v2.0/token"

A palavra “common” é o problema.
Parece que isso precisa ser substituído pelo ID do tenant para o tenant único.
Se você tiver uma conta da Microsoft, encontrará seu ID de tenant aqui: Microsoft Azure

Ainda não tentei fazer a alteração. Talvez eu faça.
Se não, qualquer pessoa que esteja pensando em usar isso para tenant único, não precisa tentar, não funcionará no momento.

Veja a imagem anexada abaixo como exemplo do tipo de erro que você receberá.

[moggleif (Morgan Johansson)]

Ok, nunca codifiquei com Ruby e faz alguns anos que não trabalho com codificação e coisas técnicas. Mas, está feito. E agora funciona também para configurações de Inquilino Único (Single Tenant).

Making Single Tenant work for the Microsoft auth plugin.

[pmusaraj (Penar Musaraj)]

Desculpe pelo acompanhamento muito, muito atrasado, o PR acima foi mesclado!

[moggleif (Morgan Johansson)]

Uhu!\n\nMinha primeira contribuição para a comunidade. Acho que não será a última.

[tobiaseigen]

Este plugin agora está incluído no core do Discourse como parte de Bundling more popular plugins with Discourse core. Se você auto-hospeda e usa o plugin, precisa removê-lo do seu app.yml antes da sua próxima atualização.