---
title: "Device Code Flow for Microsoft Graph"
canonical: "https://help.agiloft.com/space/HELP/128581641/Device+Code+Flow+for+Microsoft+Graph"
format: markdown
---
This article guides you through the steps required to integrate Agiloft CLM with Exchange Online mailboxes using the Microsoft Graph API with OAuth 2.0 device authorization grant flow. 

> 📝 For a more secure integration, Microsoft recommends using client credentials grant flow and has introduced [policies](https://techcommunity.microsoft.com/blog/microsoft-entra-blog/new-microsoft-managed-policies-to-raise-your-identity-security-posture/4286758) that may complicate the use of device code flow. If possible, use client credentials flow instead. See [Client Credentials Flow for Microsoft Graph](https://agiloft-public.atlassian.net/wiki/spaces/HELP/pages/127434860) for instructions.

Since most systems benefit from setting up an outbound account and at least one inbound account, the instructions set up both outbound and inbound email.

> Macro (include)

> ℹ️ **Prerequisites**
> ℹ️ 
> ℹ️ - To complete the setup, you need admin access to the Entra admin center with permission to configure new applications.
> ℹ️ - We recommend you create at least one separate email account exclusively for use with Agiloft CLM.
> ℹ️   - At a minimum, you need one account to use as the default outbound address.
> ℹ️   - If you're setting up inbound email, you need an account to use as the inbound address. You can use the same mailbox for both outbound and inbound email. Many systems create an address like table_name@yourdomain.com, such as contracts@yourdomain.com for the Contracts table, and use this address for both inbound and outbound email.
> ℹ️   - Accounts used for inbound email must use an “inbox” folder. Agiloft CLM can’t be configured to access to other folders.
> ℹ️   - If you plan to set up additional inbound or outbound accounts, you also need email accounts for those addresses. The setup of multiple outbound accounts is rarely implemented for Agiloft systems. For information on using them, see [Add Optional Outbound Accounts for Tables](https://agiloft-public.atlassian.net/wiki/spaces/HELP/pages/43714505). Instructions for connecting multiple inbound accounts are included in this article.
> ℹ️   - Though you can use the same email address for the default outbound account and one inbound account, you can't use the same address for multiple inbound accounts. To minimize issues, prevent collisions, and ensure incoming messages are routed correctly, each table must have a distinct inbox.
> ℹ️   - You need the credentials for these accounts to complete the authorization with Microsoft after setting up email in Agiloft CLM.
> ℹ️ - We don't recommend using shared mailboxes. Since shared mailboxes don't have credentials and can't be authenticated with OAuth, you can't connect Agiloft CLM directly to them. The setup is more straightforward and reliable if you configure regular licensed Exchange Online accounts as Agiloft CLM's inbound and outbound mailboxes.

# > Macro (anchor)

Register Agiloft CLM in Entra

Before setting up email in Agiloft CLM, you need to register Agiloft CLM as an app in Entra ID.

> ℹ️ If the options you see in the admin center or your practices for registering applications differ from those described here, refer to Microsoft's [documentation](https://docs.microsoft.com/en-us/azure/active-directory/develop/quickstart-register-app) on app registration to complete the task.

1. Sign in to the Entra admin center as an administrator with permission to configure new applications.
2. If your account has access to multiple tenants, make sure the appropriate tenant is selected.
3. Go to **Identity > Applications > App registrations** and select New registration.
4. Enter a name for the registration. For example, you might name your registration "Agiloft Graph Email."
5. Select the appropriate option for which accounts can use the application. This choice depends on the IT security policy for your organization.
6. Leave the Redirect URI empty.
7. Click Register. The admin center automatically directs you to the overview page for the Agiloft application.
8. Copy the Application (client) ID and Directory (tenant) ID from the overview page. Store these in a note so you can refer to them later.

Now that Agiloft is registered, you can configure access to the app.

# > Macro (anchor)

Configure the App

Follow the steps below to configure the app for use.

1. In the Entra admin center, click API Permissions in the sidebar.
2. Click Add a permission and choose Microsoft Graph.
3. Click Delegated permissions and select all of the OpenId permissions:
  - email
  - openid
  - offline_access
  - profile
4. In the Select permissions field, search and select Mail.Send.
5. If you plan to enable inbound email, search and select Mail.ReadWrite and IMAP.AccessAsUser.All as well.
6. Click Add permissions to add the selected permissions to the Configured permissions list.
7. Next, click Authentication in the sidebar and enable Allow Public Client Flow, then click Save.
8. At the top of the Authentication page, click Add a platform, click Web, and enter the base URL for your KB as the redirect URL. The base URL usually starts with `https://` and ends with`.com` or other top-level domain. For example: `https://example.agiloft.com`
9. Click Configure.

Now that the app is configured, you can set up outbound email in Agiloft.

# > Macro (anchor)

Set Up Outbound Email

Follow the steps below to set up the default outbound account in Agiloft. You need the Application (client) ID and Directory (tenant) ID you copied when registering Agiloft in Entra. You also need the credentials for the outbound email account so you can complete the OAuth registration with Microsoft.

1. In Agiloft, go to **Setup > System > Manage Global Variables.**
2. Go to the Variables with Default Values tab and edit the [Custom SMTP Configuration Properties](https://agiloft-public.atlassian.net/wiki/spaces/HELP/pages/43713942) global variable. To make things easier, maximize the modal window and drag the bottom corner of the Global Variable Value input box to make it bigger.
3. Paste this code into the Global Variable Value input box. Do not save it yet.

> 📝 The code below is for services hosted in Microsoft’s standard commercial cloud (microsoft.com). If your services are hosted in a sovereign cloud, use the code in [Sovereign Cloud Custom SMTP Configuration Properties](#sovereign_smtp_properties) instead.

```
mail.smtp.auth.mechanisms=XOAUTH2
mail.agiloft.smtp.auth_flow=device
mail.agiloft.smtp.client.id=CLIENT_ID
mail.agiloft.smtp.tenant.id=TENANT_ID
# DO NOT specify in case the refresh token long live time is undefined!
# mail.agiloft.smtp.refresh-token.llt=
# device authorization request
mail.agiloft.smtp.device-auth-request.url=https://login.microsoftonline.com/${mail.agiloft.smtp.tenant.id}/oauth2/v2.0/devicecode
mail.agiloft.smtp.device-auth-request.payload.1=client_id=${mail.agiloft.smtp.client.id}
mail.agiloft.smtp.device-auth-request.payload.2=scope=user.read offline_access openid profile email https://outlook.office365.com/Mail.Send
mail.agiloft.smtp.device-auth-request.response.code.name=device_code
#mail.agiloft.smtp.device-auth-request.response.expires_in.name=expires_in
mail.agiloft.smtp.device-auth-request.response.message.name=message
# device access token request
mail.agiloft.smtp.device-token.url=https://login.microsoftonline.com/${mail.agiloft.smtp.tenant.id}/oauth2/v2.0/token
mail.agiloft.smtp.device-token.payload.1=grant_type=urn:ietf:params:oauth:grant-type:device_code
mail.agiloft.smtp.device-token.payload.2=code=%CODE%
mail.agiloft.smtp.device-token.payload.3=client_id=${mail.agiloft.smtp.client.id}
mail.agiloft.smtp.device-token.response.access_token.name=access_token
mail.agiloft.smtp.device-token.response.expire.name=expires_in
mail.agiloft.smtp.device-token.response.refresh_token.name=refresh_token
# new token and refresh token
mail.agiloft.smtp.device-token-refresh.url=https://login.microsoftonline.com/${mail.agiloft.smtp.tenant.id}/oauth2/v2.0/token
mail.agiloft.smtp.device-token-refresh.payload.1=client_id=${mail.agiloft.smtp.client.id}
mail.agiloft.smtp.device-token-refresh.payload.2=scope=user.read offline_access openid profile email https://outlook.office365.com/Mail.Send
mail.agiloft.smtp.device-token-refresh.payload.3=redirect_uri=BASE_KB_URI
mail.agiloft.smtp.device-token-refresh.payload.4=grant_type=refresh_token
mail.agiloft.smtp.device-token-refresh.payload.5=refresh_token=%REFRESH_TOKEN%
mail.agiloft.smtp.device-token-refresh.response.access_token.name=access_token
mail.agiloft.smtp.device-token-refresh.response.expire.name=expires_in
mail.agiloft.smtp.device-token-refresh.response.refresh_token.name=refresh_token
```

4. Locate the following placeholders and replace them with your values. Make sure to replace only the placeholder text. Do not remove the equals sign (=) or any other text on the line.
  - **CLIENT_ID**: In line 3, replace `CLIENT_ID` with your Application (client) ID.
  - **TENANT_ID**: In line 4, replace `TENANT_ID` with your Directory (tenant) ID.
  - **BASE_KB_URI**: In line 26, replace `BASE_KB_URI` with the base URI for your KB. This is the same value as the redirect URL you specified when you registered the application. The base URI usually starts with `https://` and ends with `.com` or other top-level domain. For example: `https://example.agiloft.com`
5. Click Finish to save your changes.
6. Now go to **Setup > Email and SMS > Configure Email Server**.
7. Set the SMTP server to: GRAPH
8. Select SSL/TLS connection and set the Port to 465.
9. In SMTP login, enter the email address for the outbound account.
10. Do not enter a password.
11. In Default outbound email address, enter the outbound email address again. The system will send all outgoing messages from this address.
12. Select the Reset checkbox at the bottom of the screen and click Finish.
13. Note the message in red at the top of the screen. Follow the instructions there to complete authentication. Make sure you sign in to Microsoft as the user account for the outbound email address.
14. Back in Agiloft, click the link to finish the wizard, then click Configure Email Server.
15. Enter an email address to send a test message to.
16. Click Finish to send the test email.

If the test is successful, the browser displays a success message. If the test fails, the browser displays an error message that describes the issue. Review the configuration and make sure the information is complete and correct.

Now that the default outbound account is set up, continue to the appropriate next step:

- If you're enabling inbound email, proceed to [Set Up Inbound Email](#inbound_setup) below.
- If you're not enabling inbound email, see [Recommended Email Setup](https://agiloft-public.atlassian.net/wiki/spaces/HELP/pages/43719340).

# > Macro (anchor)

Set Up Inbound Email

> Macro (include)

You need the Application (client) ID and Directory (tenant) ID you copied previously. You also need the credentials for the inbound email account so you can complete the OAuth registration with Microsoft.

1. Go to **Setup > Email and SMS > Inbound Email Accounts**. This list includes all existing inbound email accounts for all tables.
2. Edit the demo configuration for Contract. If you already configured Contract and are adding another inbound account, select a different demo configuration to modify or click New to create a new configuration.
3. On the Table tab, if the table isn't already selected because this is a new configuration, select the table that will receive inbound email. If you're editing an existing configuration, the table is already selected.
4. Click Next.
5. On the Server tab, select IMAP (Microsoft Exchange) and enter: GRAPH:GRAPH
6. Leave SSL/TLS connection unchecked and Custom Port as 143.
7. Paste the following code into the text input box. If the input box isn't shown, go to the last tab and click Finish. Then reopen this configuration and return to the Server tab, which now displays the input box.

> 📝 The code below is for services hosted in Microsoft’s standard commercial cloud (microsoft.com). If your services are hosted in a sovereign cloud, use the code in [Sovereign Cloud Inbound Server Configuration Properties](#sovereign_server_properties) instead.

```plaintext
mail.inbound.auth.mechanisms=XOAUTH2
mail.agiloft.inbound.auth_flow=device
mail.agiloft.inbound.trace=false
mail.agiloft.inbound.client.id=CLIENT_ID
mail.agiloft.inbound.tenant.id=TENANT_ID
# DO NOT specify in case the refresh token long live time is undefined!
# mail.agiloft.inbound.refresh-token.llt=
# device authorization request
mail.agiloft.inbound.device-auth-request.url=https://login.microsoftonline.com/${mail.agiloft.inbound.tenant.id}/oauth2/v2.0/devicecode
mail.agiloft.inbound.device-auth-request.payload.1=client_id=${mail.agiloft.inbound.client.id}
mail.agiloft.inbound.device-auth-request.payload.2=scope=user.read offline_access openid profile email https://outlook.office365.com/Mail.ReadWrite
mail.agiloft.inbound.device-auth-request.response.code.name=device_code
#mail.agiloft.inbound.device-auth-request.response.expires_in.name=expires_in
mail.agiloft.inbound.device-auth-request.response.message.name=message
# device access token request
mail.agiloft.inbound.device-token.url=https://login.microsoftonline.com/${mail.agiloft.inbound.tenant.id}/oauth2/v2.0/token
mail.agiloft.inbound.device-token.payload.1=grant_type=urn:ietf:params:oauth:grant-type:device_code
mail.agiloft.inbound.device-token.payload.2=code=%CODE%
mail.agiloft.inbound.device-token.payload.3=client_id=${mail.agiloft.inbound.client.id}
mail.agiloft.inbound.device-token.response.access_token.name=access_token
mail.agiloft.inbound.device-token.response.expire.name=expires_in
mail.agiloft.inbound.device-token.response.refresh_token.name=refresh_token
# new token and refresh token
mail.agiloft.inbound.device-token-refresh.url=https://login.microsoftonline.com/${mail.agiloft.inbound.tenant.id}/oauth2/v2.0/token
mail.agiloft.inbound.device-token-refresh.payload.1=client_id=${mail.agiloft.inbound.client.id}
mail.agiloft.inbound.device-token-refresh.payload.2=scope=user.read offline_access openid profile email https://outlook.office365.com/Mail.ReadWrite
mail.agiloft.inbound.device-token-refresh.payload.3=redirect_uri=BASE_KB_URI
mail.agiloft.inbound.device-token-refresh.payload.4=grant_type=refresh_token
mail.agiloft.inbound.device-token-refresh.payload.5=refresh_token=%REFRESH_TOKEN%
mail.agiloft.inbound.device-token-refresh.response.access_token.name=access_token
mail.agiloft.inbound.device-token-refresh.response.expire.name=expires_in
mail.agiloft.inbound.device-token-refresh.response.refresh_token.name=refresh_token
```

8. Locate the following placeholders and replace them with your credentials:
  - **CLIENT_ID**: In line 4, replace `CLIENT_ID` with your Application (client) ID.
  - **TENANT_ID**: In line 5, replace `TENANT_ID` with your Directory (tenant) ID.
  - **BASE_KB_URI**: In line 27, replace `BASE_KB_URI` with the base URI for your KB. This is the same value as the redirect URL you specified when you registered the application. The base URI usually starts with `https://` and ends with `.com` or other top-level domain. For example: `https://example.agiloft.com`
9. Click Next.
10. On the Account tab, note the warning message at the top of the screen. Follow the instructions there to complete authentication. When you sign in to Microsoft, sign in as the user for the inbound email address.
11. Back in Agiloft on the Account tab, enter the following:
  1. In the Email and Email Account fields, enter the complete inbound email address.
  2. Leave the Password field empty. If a series of dots has replaced a previously blank password, delete them.
  3. Under Activity, select This account is actively polling for emails. This enables Agiloft to read messages in the mailbox and pull them into the KB. When "Disable this account - do not check for emails" is selected, it means the inbound account still receives messages, but Agiloft won't access them to pull them into the system.
  4. If incoming messages are saved to a folder other than Inbox, enter the folder path where Agiloft should check for incoming emails.
  5. Click Next.
12. Confirm that a message appears stating the account is valid. If you see an error message, retrace your steps and check your work.
13. Go to the last tab and click Finish. The default settings on the rest of the tabs are ideal for most use cases, and we don't recommend that you change them.

For more information on how Agiloft checks inbound email, see [Inbound Email Processing](https://agiloft-public.atlassian.net/wiki/spaces/HELP/pages/43719338).

If you want to set up an inbound account for another table, repeat the steps above. If you've finished setting up inbound accounts, see [Recommended Email Setup](https://agiloft-public.atlassian.net/wiki/spaces/HELP/pages/43719340).

# > Macro (anchor)

Sovereign Cloud Integrations

Integrating with Microsoft services hosted in a sovereign cloud requires additional customization when configuring the outbound email SMTP properties and inbound server properties. This section provides the code to use in place of the contents supplied in the outbound and inbound email setup instructions above. These templates include additional placeholders that need to be replaced.

## > Macro (anchor)

Sovereign Cloud Custom SMTP Configuration Properties

When setting the [Custom SMTP Configuration Properties](https://agiloft-public.atlassian.net/wiki/spaces/HELP/pages/43713942) global variable, use the following content in place of the code shown in Step 3 in [Set Up Outbound Email](#outbound_setup). Replace each placeholder with the appropriate value for your cloud service. [Placeholder descriptions](#placeholder_descriptions) are provided below. 

```
mail.smtp.auth.mechanisms=XOAUTH2
mail.agiloft.smtp.auth_flow=device
mail.agiloft.smtp.client.id=CLIENT_ID
mail.agiloft.smtp.tenant.id=TENANT_ID
# DO NOT specify in case the refresh token long live time is undefined!
# mail.agiloft.smtp.refresh-token.llt=
# device authorization request
mail.agiloft.smtp.device-auth-request.url=https://ENTRA_DOMAIN/${mail.agiloft.smtp.tenant.id}/oauth2/v2.0/devicecode
mail.agiloft.smtp.device-auth-request.payload.1=client_id=${mail.agiloft.smtp.client.id}
mail.agiloft.smtp.device-auth-request.payload.2=scope=user.read offline_access openid profile email https://EXCHANGE_DOMAIN/Mail.Send
mail.agiloft.smtp.device-auth-request.response.code.name=device_code
#mail.agiloft.smtp.device-auth-request.response.expires_in.name=expires_in
mail.agiloft.smtp.device-auth-request.response.message.name=message
# device access token request
mail.agiloft.smtp.device-token.url=https://ENTRA_DOMAIN/${mail.agiloft.smtp.tenant.id}/oauth2/v2.0/token
mail.agiloft.smtp.device-token.payload.1=grant_type=urn:ietf:params:oauth:grant-type:device_code
mail.agiloft.smtp.device-token.payload.2=code=%CODE%
mail.agiloft.smtp.device-token.payload.3=client_id=${mail.agiloft.smtp.client.id}
mail.agiloft.smtp.device-token.response.access_token.name=access_token
mail.agiloft.smtp.device-token.response.expire.name=expires_in
mail.agiloft.smtp.device-token.response.refresh_token.name=refresh_token
# new token and refresh token
mail.agiloft.smtp.device-token-refresh.url=https://ENTRA_DOMAIN/${mail.agiloft.smtp.tenant.id}/oauth2/v2.0/token
mail.agiloft.smtp.device-token-refresh.payload.1=client_id=${mail.agiloft.smtp.client.id}
mail.agiloft.smtp.device-token-refresh.payload.2=scope=user.read offline_access openid profile email https://EXCHANGE_DOMAIN/Mail.Send
mail.agiloft.smtp.device-token-refresh.payload.3=redirect_uri=BASE_KB_URI
mail.agiloft.smtp.device-token-refresh.payload.4=grant_type=refresh_token
mail.agiloft.smtp.device-token-refresh.payload.5=refresh_token=%REFRESH_TOKEN%
mail.agiloft.smtp.device-token-refresh.response.access_token.name=access_token
mail.agiloft.smtp.device-token-refresh.response.expire.name=expires_in
mail.agiloft.smtp.device-token-refresh.response.refresh_token.name=refresh_token
mail.graph.endpoint=GRAPH_SERVICE_ENDPOINT
```

## > Macro (anchor)

Sovereign Cloud Inbound Server Configuration Properties

When setting inbound email server properties, use the following content in place of the code shown in Step 7 in [Set Up Inbound Email](#inbound_setup). Replace each placeholder with the appropriate value for your cloud service. [Placeholder descriptions](#placeholder_descriptions) are provided below.

```
mail.inbound.auth.mechanisms=XOAUTH2
mail.agiloft.inbound.auth_flow=device
mail.agiloft.inbound.trace=false
mail.agiloft.inbound.client.id=CLIENT_ID
mail.agiloft.inbound.tenant.id=TENANT_ID
# DO NOT specify in case the refresh token long live time is undefined!
# mail.agiloft.inbound.refresh-token.llt=
# device authorization request
mail.agiloft.inbound.device-auth-request.url=https://ENTRA_DOMAIN/${mail.agiloft.inbound.tenant.id}/oauth2/v2.0/devicecode
mail.agiloft.inbound.device-auth-request.payload.1=client_id=${mail.agiloft.inbound.client.id}
mail.agiloft.inbound.device-auth-request.payload.2=scope=user.read offline_access openid profile email https://EXCHANGE_DOMAIN/Mail.ReadWrite
mail.agiloft.inbound.device-auth-request.response.code.name=device_code
#mail.agiloft.inbound.device-auth-request.response.expires_in.name=expires_in
mail.agiloft.inbound.device-auth-request.response.message.name=message
# device access token request
mail.agiloft.inbound.device-token.url=https://ENTRA_DOMAIN/${mail.agiloft.inbound.tenant.id}/oauth2/v2.0/token
mail.agiloft.inbound.device-token.payload.1=grant_type=urn:ietf:params:oauth:grant-type:device_code
mail.agiloft.inbound.device-token.payload.2=code=%CODE%
mail.agiloft.inbound.device-token.payload.3=client_id=${mail.agiloft.inbound.client.id}
mail.agiloft.inbound.device-token.response.access_token.name=access_token
mail.agiloft.inbound.device-token.response.expire.name=expires_in
mail.agiloft.inbound.device-token.response.refresh_token.name=refresh_token
# new token and refresh token
mail.agiloft.inbound.device-token-refresh.url=https://ENTRA_DOMAIN/${mail.agiloft.inbound.tenant.id}/oauth2/v2.0/token
mail.agiloft.inbound.device-token-refresh.payload.1=client_id=${mail.agiloft.inbound.client.id}
mail.agiloft.inbound.device-token-refresh.payload.2=scope=user.read offline_access openid profile email https://EXCHANGE_DOMAIN/Mail.ReadWrite
mail.agiloft.inbound.device-token-refresh.payload.3=redirect_uri=BASE_KB_URI
mail.agiloft.inbound.device-token-refresh.payload.4=grant_type=refresh_token
mail.agiloft.inbound.device-token-refresh.payload.5=refresh_token=%REFRESH_TOKEN%
mail.agiloft.inbound.device-token-refresh.response.access_token.name=access_token
mail.agiloft.inbound.device-token-refresh.response.expire.name=expires_in
mail.agiloft.inbound.device-token-refresh.response.refresh_token.name=refresh_token
mail.graph.endpoint=GRAPH_SERVICE_ENDPOINT
```

## > Macro (anchor)

Placeholder Descriptions

This section describes the placeholders to replace in the code. Make sure to replace only the placeholder text. Do not remove the equals sign (=) or any other surrounding text.

**CLIENT_ID**  
Near the top of the text, replace `CLIENT_ID` with your Application (client) ID.

**TENANT_ID**  
Near the top of the text, replace `TENANT_ID` with your Directory (tenant) ID.

**ENTRA_DOMAIN**  
In three places, replace `ENTRA_DOMAIN` with the [Entra authorization endpoint](https://learn.microsoft.com/en-us/entra/identity-platform/authentication-national-cloud#microsoft-entra-authentication-endpoints) domain for your cloud deployment. The table below lists the values for each cloud. 

| **Cloud** | **Entra Domain** |
| --- | --- |
| Microsoft Entra ID for US Government | login.microsoftonline.us |
| Microsoft Entra China operated by 21Vianet | login.partner.microsoftonline.cn |

**EXCHANGE_DOMAIN**  
In two places, replace `EXCHANGE_DOMAIN` with the Exchange Online domain for your [Microsoft 365 endpoint](https://learn.microsoft.com/en-us/microsoft-365/enterprise/microsoft-365-endpoints). The table below lists the values for each cloud.

| **Cloud** | **Exchange Domain** |
| --- | --- |
| U.S. Government GCC High endpoints | outlook.office365.us |
| U.S. Government DoD endpoints | outlook-dod.office365.us |
| Microsoft 365 operated by 21Vianet endpoints | partner.outlook.cn |

**BASE_KB_URI**  
Near the bottom of the text, replace `BASE_KB_URI` with the base URI for your KB. This is the same value as the redirect URL you specified when you registered the application. The base URI usually starts with `https://` and ends with `.com` or other top-level domain. For example: `https://example.agiloft.com`

**GRAPH_SERVICE_ENDPOINT**  
In the last line, replace `GRAPH_SERVICE_ENDPOINT` with the service root endpoint for your [Microsoft Graph national cloud deployment](https://learn.microsoft.com/en-us/graph/deployments). The table below lists the endpoints for each cloud.

| **Cloud** | **Graph Endpoint** |
| --- | --- |
| Microsoft Graph for US Government L4 (GCC High) | https://graph.microsoft.us/v1.0 |
| Microsoft Graph for US Government L5 (DOD) | https://dod-graph.microsoft.us/v1.0 |
| Microsoft Graph China operated by 21Vianet | https://microsoftgraph.chinacloudapi.cn/v1.0 |

#### Related articles

> Macro (contentbylabel)