Microsoft as your sign in option

Easily add Microsoft Sign In to your app with Scalekit

Overview

Scalekit enables apps to easily let users sign in using Microsoft as their social connector. This guide walks you through the process of setting up the connection between Scalekit and Microsoft, and using the Scalekit SDK to add "Sign in with Microsoft" to your application.

A diagram showing "Your Application" connecting to "Scalekit" via OpenID Connect, which links to Microsoft using OAuth 2.0.

By the end of this guide, you will be able to:

1. Set up an OAuth 2.0 connection between Scalekit and Microsoft
2. Scalekit SDK to add "Sign in with Microsoft" to your application

Connect Microsoft with Scalekit

Navigate to Social Login settings

Open your Scalekit dashboard and navigate to Social Login under the Authentication section.

Scalekit dashboard showcasing social login setup with various platform integration options.

Add a new Microsoft connection

Click the "+ Add Connection" button and select Microsoft from the list of available options.

Add social login connections: Microsoft

Configure OAuth settings

The OAuth Configuration details page helps you set up the connection:

• Note the Redirect URI provided for your app. You'll use this URL to register with Microsoft.
• Client ID and Client Secret are generated by Microsoft when you register an OAuth App. They enable Scalekit to authenticate your app and establish trust with Microsoft.

Microsoft OAuth configuration in Scalekit, showing redirect URI, client credentials, and scopes for social login setup.

Set up Microsoft OAuth 2.0

Microsoft lets you set up OAuth through the Mircosoft Identity Platform. Follow Microsoft's instructions to set up OAuth 2.0.

• Use the Redirect URI from Scalekit as the Redirect URI in Microsoft's setup
• Copy the generated Client ID and Client Secret into the Scalekit Dashboard

After completing the setup, click "Save Changes" in Scalekit for the changes to take effect.

Microsoft OAuth configuration for social login, showing redirect URI, client ID, and scopes for authentication.

Choose the user experience for login prompt

Scalekit offers flexibility to control how and when users are prompted for reauthentication, consent, or account selection. Below are the available options for customizing user sign-in behavior:

• Auto Sign-in (default): Automatically completes the login process without showing any confirmation prompts. This is ideal for single account users who are already logged in and have previously provided consent.

• Consent: The authorization server triggers a consent screen after sign-in, asking the user to grant permissions to the app.

• Select Account: The authorization server prompts the user to select a user account. This allows a user who has multiple accounts at the authorization server to select amongst the multiple accounts that they may have current sessions for.

• Login: Forces the user to re-enter their credentials and log in, even if a valid session already exists.

• None: Performs a background authentication check without displaying any screens. If the user is not authenticated or hasn't provided consent, an error will be returned.

Test the Connection

Click the "Test Connection" button in Scalekit. You will be redirected to the Microsoft Consent screen to authorize access. A summary table will show the information that will be sent to your app.

Test connection success, showing the consent screen and summary table.

Next steps

Once the connection is set up, refer to our Quickstart guide to learn how to integrate this connection into your app using the Scalekit SDK.