> ## Documentation Index > Fetch the complete documentation index at: https://nango.dev/docs/llms.txt > Use this file to discover all available pages before exploring further. # How to register your own Microsoft Teams OAuth app > Register an OAuth app with Microsoft Teams and connect it to Nango This guide shows you how to register your own app with Microsoft Teams (via Microsoft Entra ID) to obtain your OAuth credentials (client id & secret). These are required to let your users grant your app access to their Microsoft Teams account. If you don't already have them, sign up for a [Microsoft account](https://account.microsoft.com/account) and an [Azure account](https://azure.microsoft.com/free). 1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least an Application Developer. 2. If you have access to multiple tenants, use the Settings icon in the top menu to switch to the tenant in which you want to register the application. 3. From the search bar at the top of the Azure portal, search for **App registrations** and select it. Then choose **New registration**. Or from your left navigation tab, navigate to **Applications** > **App registrations** then choose **New registration**. 4. Enter a meaningful name for your application, for example "Nango Integration". 5. Under **Supported account types** you need to decide who can install your integration: * **Accounts in any organizational directory** - Any user account in a professional Microsoft organization (Business, School, etc.) * **Accounts in any organizational directory and personal Microsoft accounts** - The accounts from the first option, plus personal Microsoft accounts (pick this unless you want to restrict your integration to business accounts) 6. Leave the **Redirect URI** section blank for now; we'll configure it in a later step. 7. Click **Register** to complete the app registration. After registration, you'll be taken to the application's Overview page. Record the **Application (client) ID**, which uniquely identifies your application and is used in your application's code as part of validating security tokens. 1. In the left sidebar, select **Authentication**. 2. Under **Platform configurations**, select **Add a platform**. 3. Select **Web** as the platform type. 4. Enter `https://api.nango.dev/oauth/callback` as the Redirect URI. 5. Under **Advanced settings**, keep **Allow public client flows** set to the default **No** for web applications. 6. Click **Configure** to save your changes. 1. In the left sidebar, select **API permissions**. 2. Click **Add a permission**. 3. Select **Microsoft Graph** to integrate with **Microsoft Teams**. 4. Select the required permissions from the **Delegated permissions section**.. 5. Select the specific permissions your app requires. Please refer to the table below for some of the [commonly used scopes](#common-scopes). 6. Click **Add permissions**. 7. If your application requires admin consent, click **Grant admin consent for \[tenant]** to pre-authorize the permissions. 1. In the left sidebar, select **Certificates & secrets**. 2. Under **Client secrets**, click **New client secret**. 3. Enter a description for the secret and select an expiration period (6 months, 12 months, 24 months, or custom). Please select a date further in the future to avoid interruptions, note that the **Custom** date can only be set to a maximum of 1 year from the current date. If the secret expires, you will need to regenerate a new one and update your integration within Nango. 4. Click **Add**. 5. **Important**: Copy the secret value immediately and store it securely. You won't be able to see it again after you leave this page. 1. In the left sidebar, select **Token configuration**. Here you can configure optional claims to be included in the access tokens issued for your application. 2. Click **Add optional claim** and select the claims you want to include in your access tokens. If you want users to see your app on their My Apps page: 1. From the search bar at the top of the Azure portal, search for **Enterprise applications**, select it, and then choose your app. 2. On the **Properties** page, set **Visible to users?** to **Yes**. Follow the [*Quickstart*](/getting-started/quickstart). ## Common Scopes You can find permissions required for each API call in their corresponding API methods section. For example, to get a user from Teams, see [Get a user permissions](https://learn.microsoft.com/en-us/graph/api/user-get?view=graph-rest-1.0\&tabs=http#permissions). Here are some commonly used scopes for Microsoft Teams: | Scope | Description | | ------------------------- | ----------------------------------------------------------- | | `offline_access` | Access to refresh tokens for offline access | | `Chat.Read` | Read the signed-in user's chat messages | | `Chat.ReadWrite` | Read and write the user's chat messages | | `ChannelMessage.Read.All` | Read all channel messages in teams the user has access to | | `ChannelMessage.Send` | Send messages to channels the user is a member of | | `Team.ReadBasic.All` | Read team names and descriptions the user has access to | | `Team.Read.All` | Read full team properties and memberships | | `Presence.Read` | Read the user's presence (availability and status) | | `Presence.Read.All` | Read presence information for all users in the organization | | `User.Read.All` | Read user profiles in the organization | For a complete list of available scopes, see [Microsoft Graph permissions reference](https://learn.microsoft.com/en-us/graph/permissions-reference). ***