@@ -15,7 +15,6 @@ Valid providers are :
1515- [Keycloak](#keycloak-auth-provider)
1616- [GitLab](#gitlab-auth-provider)
1717- [LinkedIn](#linkedin-auth-provider)
18−- [Microsoft Azure AD](#microsoft-azure-ad-provider)
1918- [OpenID Connect](#openid-connect-provider)
2019- [login.gov](#logingov-provider)
2120- [Nextcloud](#nextcloud-provider)
@@ -87,7 +86,7 @@ Note: The user is checked against the group members list on initial authenticati
8786 --oidc-issuer-url=https://sts.windows.net/{tenant-id}/
8887```
8988
90−Note: When using the Azure Auth provider with nginx and the cookie session store you may find the cookie is too large and doesn't get passed through correctly. Increasing the proxy_buffer_size in nginx or implementing the [redis session storage](sessions.md#redis-storage) should resolve this.
89+Note: When using the Azure Auth provider with nginx and the cookie session store you may find the cookie is too large and doesn't get passed through correctly. Increasing the `proxy_buffer_size` in nginx or implementing the [redis session storage](sessions.md#redis-storage) should resolve this.
9190
9291### ADFS Auth Provider
9392
@@ -234,12 +233,6 @@ For LinkedIn, the registration steps are:
2342333. Fill in the remaining required fields and Save.
2352344. Take note of the **Consumer Key / API Key** and **Consumer Secret / Secret Key**
236235
237−### Microsoft Azure AD Provider
238−
239−For adding an application to the Microsoft Azure AD follow [these steps to add an application](https://docs.microsoft.com/en-us/azure/active-directory/develop/quickstart-register-app).
240−
241−Take note of your `TenantId` if applicable for your situation. The `TenantId` can be used to override the default `common` authorization server with a tenant specific server.
242−
243236### OpenID Connect Provider
244237
245238OpenID Connect is a spec for OAUTH 2.0 + identity that is implemented by many major providers and several open source projects.