Microsoft Azure OAuth2 OmniAuth Provider

To enable the Microsoft Azure OAuth2 OmniAuth provider you must register your application with Azure. Azure will generate a client ID and secret key for you to use.

  1. Sign in to the Azure Management Portal.

  2. Select "Active Directory" on the left and choose the directory you want to use to register GitLab.

  3. Select "Applications" at the top bar and click the "Add" button the bottom.

  4. Select "Add an application my organization is developing".

  5. Provide the project information and click the "Next" button.

    • Name: 'GitLab' works just fine here.
  6. On the "App properties" page enter the needed URI's and click the "Complete" button.

  7. Select "Configure" in the top menu.

  8. Add a "Reply URL" pointing to the Azure OAuth callback of your GitLab installation (e.g.

  9. Create a "Client secret" by selecting a duration, the secret will be generated as soon as you click the "Save" button in the bottom menu..

  10. Note the "CLIENT ID" and the "CLIENT SECRET".

  11. Select "View endpoints" from the bottom menu.

  12. You will see lots of endpoint URLs in the form ' ID/...', note down the TENANT ID part of one of those endpoints.

  13. On your GitLab server, open the configuration file.

    For omnibus package:

      sudo editor /etc/gitlab/gitlab.rb

    For installations from source:

      cd /home/git/gitlab
      sudo -u git -H editor config/gitlab.yml
  14. See Initial OmniAuth Configuration for initial settings.

  15. Add the provider configuration:

    For omnibus package:

      gitlab_rails['omniauth_providers'] = [
          "name" => "azure_oauth2",
          "args" => {
            "client_id" => "CLIENT ID",
            "client_secret" => "CLIENT SECRET",
            "tenant_id" => "TENANT ID",

    For installations from source:

     - { name: 'azure_oauth2',
       args: { client_id: "CLIENT ID",
       client_secret: "CLIENT SECRET",
       tenant_id: "TENANT ID" } }
  16. Replace 'CLIENT ID', 'CLIENT SECRET' and 'TENANT ID' with the values you got above.

  17. Save the configuration file.

  18. Restart GitLab for the changes to take effect.

On the sign in page there should now be a Microsoft icon below the regular sign in form. Click the icon to begin the authentication process. Microsoft will ask the user to sign in and authorize the GitLab application. If everything goes well the user will be returned to GitLab and will be signed in.