# Amazon Quick Microsoft Word extension The Quick extension for Microsoft Word integrates AI-powered assistance directly into your document creation and editing workflows. Users can access Quick capabilities within Word to enhance their document productivity and content quality without switching between applications. The Word extension enables users to: + Review, draft, and revise documents with AI assistance. + Summarize documents and get insights. + Simplify and improve writing quality. + Use actions from action connectors configured in Amazon Quick. + Access any company knowledge sources added to your Amazon Quick instance from within Microsoft Word. **Important** The Amazon Quick customer integrating Microsoft Word must have a paid Word organization with an *M365 subscription for their organization*. Amazon Quick does not use user data for service improvement or for training its underlying large language models (LLMs). **Topics** + [Prerequisites for Microsoft Word extension](#word-prerequisites) + [Configure Microsoft Word extension access](#configure-word-extension) ## Prerequisites for Microsoft Word extension Before adding the Amazon Quick extension to Microsoft Word, administrators must complete the following steps: 1. Have a Microsoft 365 Business subscription and be a Global Admin or have administrative permissions (specifically `AppCatalog.ReadWrite.All`). 1. Have a Amazon Quick instance. 1. Your Microsoft 365 tenant ID. You can find this by going to the Azure portal > **Azure Active Directory** > **Properties**, or by using PowerShell. For detailed steps, see [How to find your tenant ID - Microsoft Entra](https://learn.microsoft.com/en-us/entra/fundamentals/how-to-find-tenant) in the Microsoft Learn portal. If you configured the authentication to connect to Amazon Quick with IAM Identity Center, complete the following additional steps: 1. Ensure you have an IAM Identity Center instance enabled on your AWS account. 1. If you are connecting an external IAM provider to IAM Identity Center, ensure that every user under your IAM provider configuration has an email associated with them. 1. If you are using Entra ID, set up SCIM identity propagation between the Microsoft Entra ID instance and IAM Identity Center. For detailed steps, see [Configure SAML and SCIM with Microsoft Entra ID and IAM Identity Center](https://docs.aws.amazon.com/singlesignon/latest/userguide/azure-ad-idp.html). ## Configure Microsoft Word extension access As an administrator, you must allow the Amazon Quick Microsoft Word Extension to connect to your Amazon Quick application environment and web experience. You can use the Amazon Quick console to manage extension access configurations. ### User attribute mapping When you configure a Microsoft Word extension, user identity is mapped by default using the following attributes: + **Amazon Quick user attribute** - Email address is used to map Amazon Quick users to their corresponding Microsoft 365 accounts. The system uses the email address to establish the connection between user identities. + **M365 Office add-in user attribute** - User Principal Name (UPN) is used to match against Microsoft 365 user accounts. Users need to use the User Principal Name (UPN) to sign in to Microsoft 365. Email address that works on both cloud and on-premise systems. These default mappings ensure secure and accurate user identification across both platforms without requiring additional configuration. **Topics** + [User attribute mapping](#word-user-attributes) + [Add Microsoft Word extension access for accounts using IAM Identity Center](#add-word-extension-access-idc) + [Add Microsoft Word extension access for accounts using other authentication methods](#add-word-extension-access) + [Edit Microsoft Word extension access](#edit-word-extension-access) + [Delete Microsoft Word extension access](#delete-word-extension-access) ### Add Microsoft Word extension access for accounts using IAM Identity Center Configuring extension access with IAM Identity Center requires completing steps specific to your identity provider (Entra ID or Okta) followed by common setup steps in AWS. #### Configure IAM Identity Center with Entra ID Follow these steps only if you are using IAM Identity Center with Entra ID to set up and configure an Azure tenant on your Microsoft Azure portal: **To set up an Azure tenant** 1. In the Azure account, create a new app registration. 1. Go to **App registrations**. 1. In the **App registrations** screen, choose **New registration**. Under the **Supported account types** option, choose **Accounts in this organizational directory only (Personal use only - Single tenant)**. Once finished, choose **Register**. 1. Note the client ID. You will need this later. 1. Create a client secret for the app registration and keep note of it. You will need this later. 1. Add callback URLs for each Region in which your Word extension will be installed. 1. Navigate to the app registration's **Authentication** tab. 1. Choose **Platform Configurations**, **Add a platform**. 1. Choose **Web**. 1. Compose a callback URL using the following format, replacing *your-region* with your Amazon Quick instance Region. The Word extension supports the following Regions: `ap-southeast-2`, `eu-west-1`, `us-west-2`, and `us-east-1`. ``` qbs-cell001.dp.appintegrations.your-region.prod.plato.ai.aws.dev/auth/idc-tti/callback ``` 1. Insert the callback URL as the redirect URI and choose **Configure** when done. Follow these steps to configure a Trusted Token Issuer on your IAM Identity Center instance in your AWS Console: **To configure a Trusted Token Issuer** 1. Go to your AWS account and navigate to your IAM Identity Center instance. 1. Navigate to **Settings**, **Authentication**. 1. Choose **Create trusted token issuer**. 1. Add the issuer URL, which should follow this template, where *Tenant ID* refers to your Entra tenant ID: ``` login.microsoftonline.com/Tenant ID/v2.0 ``` **Note** The issuer URL should be the OIDC discovery endpoint of your identity without the well-known document URI path. If you include the well-known document URI path, this will not work. See Trusted token issuer configuration settings. 1. Choose **Email** as the Identity Provider attribute and IAM Identity Center attribute. 1. Note the trusted token issuer ARN. You will need this in a later step. After completing these Entra ID-specific steps, proceed to the [Complete AWS Configuration (all providers)](#complete-aws-config-word) section below. #### Configure IAM Identity Center with Okta Follow these steps only if you are using IAM Identity Center with Okta to set up and configure your App Integration in the Okta Admin console: **To set up an Okta Application** 1. In your Okta account, create a new Okta App Integration. 1. In your Okta Admin console, navigate to **Applications** > **Applications**. 1. Click on **Create App Integration**. 1. For the Sign-in method, select **OIDC - OpenID Connect**. 1. For the Application type, select **Web Application**. 1. Click on **Next**. 1. Provide an App integration name. 1. Under **Grant type** > **Core grants**, ensure **Authorization Code** and **Refresh Token** are selected. 1. Under **Grant type** > **Advanced** > **Other grants**, ensure **Implicit (hybrid)** is selected. 1. Add callback URIs for each Region in which your Word extension will be installed 1. Compose a callback URI using the following format, replacing *your-region* with your Amazon Quick instance Region for each region where you wish to configure the extension. The Word extension supports the following Regions: `ap-southeast-2`, `eu-west-1`, `us-west-2`, and `us-east-1`. ``` qbs-cell001.dp.appintegrations.your-region.prod.plato.ai.aws.dev/auth/idc-tti/callback ``` 1. Under **Sign-in redirect URIs**, click on **Add URI** and paste each of the URIs you generated from the previous step. 1. Provide your organization access to the app: 1. Under **Assignments** > **Controlled access**, select the groups in your organization that need to have access. 1. Under **Assignments** > **Enable immediate access**, select **Enable immediate access with Federation Broker Mode**. 1. Click on **Save**. 1. Note down the **Client ID** and **Client Secret** for the app integration you just created. You will need this in the next steps. **To configure a Trusted Token Issuer** 1. Go to your AWS account and navigate to your IAM Identity Center instance. 1. Navigate to **Settings** > **Authentication**. 1. Choose **Create trusted token issuer**. 1. Add the issuer URL, which should follow this template, where *yourOktaDomain* refers to the okta URL for your organization, which may look like `your-organization.okta.com`: ``` https://{yourOktaDomain}/oauth2/default ``` **Note** The issuer URL should be the OIDC discovery endpoint of your identity without the well-known document URI path. If you include the well-known document URI path, this will not work. See Trusted token issuer configuration settings. 1. Choose **Email** as the Identity Provider attribute and IAM Identity Center attribute. 1. Note the trusted token issuer ARN. You will need this in a later step. After completing these Okta-specific steps, proceed to the [Complete AWS Configuration (all providers)](#complete-aws-config-word) section below. #### Complete AWS Configuration (all providers) Follow these steps to set up permissions on AWS Console: **To set up permissions** 1. Navigate to Secrets Manager on AWS console. 1. Choose **Store a new secret**. 1. Choose **Other type of secret** and choose the **Plaintext** tab. 1. Your secret should be in the following format and use the app registration client ID and app registration client secret that you saved from the earlier steps: ``` { "client_id":"Your app registration client ID", "client_secret":"Your app registration client secret" } ``` 1. Navigate to the secret you just created and save the ARN for later. 1. Now navigate to IAM on AWS console. 1. Choose **Access Management**, **Roles** in the left navigation bar. 1. Choose **Create role**. 1. Choose **Custom trust policy**. 1. Configure the role to trust our service principal for the relevant Region that you selected when configuring your identity provider app integration by adding the following statement replacing *your-region* with the Region you chose when creating your identity provider app integration: ``` { "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Principal": { "Service": "your-region.prod.appintegrations.plato.aws.internal" }, "Action": "sts:AssumeRole", "Condition": {} } ] } ``` 1. Choose **Next**. 1. Provide a name and description and choose **Create role**. 1. Navigate to the role you just created and choose it. 1. Choose **Add Permissions**, **Create inline policy**. 1. Choose **JSON**. 1. Configure the role with permissions to read secrets from Secrets Manager and permissions to invoke `sso:DescribeTrustedTokenIssuer` by adding the following statement: ``` { "Version": "2012-10-17", "Statement": [ { "Sid": "BasePermissions", "Effect": "Allow", "Action": [ "secretsmanager:GetSecretValue", "sso:DescribeTrustedTokenIssuer" ], "Resource": "*" } ] } ``` 1. Provide a policy name and choose **Create policy**. 1. Copy and save the ARN of the IAM role you created for later. You will need it in the next steps. Now you can follow these steps to create a new extension access configuration that will allow Amazon Quick to integrate with your Microsoft Word environment: **To create an extension access configuration** 1. Sign in to the Amazon Quick console. 1. In the top right, choose the profile picture icon. 1. From the drop-down menu, choose **Manage account**. 1. Under **Permissions**, choose **Extension access**. 1. In the top right, choose **New extension access**. 1. If this is your first time setting up extension access, you are prompted to complete the **Trusted Token Issuer Setup**. Configure the following fields and then choose **Next**: + **Trusted Token Issuer ARN** – Enter the trusted token issuer ARN that you noted from the earlier steps. + **Aud claim** – Enter the client ID from your app registration (Entra ID) or app integration (Okta) that you saved from the earlier steps. **Note** This is a one-time setup that establishes a trusted identity source for all extensions. Once completed, you won't need to do this again for other extension accesses. 1. Select **Microsoft Word**. Then, choose **Next**. 1. Configure the following fields: + **Name** - A name for your extension is pre-filled for you. You can edit this and enter a descriptive name for the Word extension (maximum 512 alphanumeric characters, hyphens allowed but no spaces). + **Description (optional)** - A description for your extension is pre-filled for you. You can edit this and enter a new description to provide additional context about this extension configuration (maximum 1000 characters). + **M365 tenant ID** - Enter your Microsoft 365 tenant identifier (must be 36 characters). + **Secrets Role ARN** - Paste the ARN of the IAM role you created from the previous steps. + **Secrets ARN** - Paste the ARN of the Secrets Manager secret you created from the previous steps. 1. Choose **Add** to save the new access configuration. A success message will open up on the top right of your screen. 1. From the success message, choose **View extensions** to finish installing your extension. **Note** You can also navigate to the installation screen from **Connections** > **Extensions** in the Amazon Quick menu. Once created, this extension access configuration enables authors and other admin in your organization to create and deploy Amazon Quick extensions within your Microsoft Word environment. **Note** For your end users to begin using your Microsoft Word extension, an admin or author must finish deploying a extension after you configure extension access. Notify your authors that they can view, edit, and complete installation of this extension under **Extensions** in the left navigation once it has been shared. To learn how to do this see Installing your Microsoft Word extension in the Microsoft Word extension author guide. ### Add Microsoft Word extension access for accounts using other authentication methods Follow these steps to create a new extension access configuration that will allow Amazon Quick to integrate with your Microsoft Word environment. 1. Sign in to the Amazon Quick console. 1. In the top right, select the profile picture icon. 1. From the drop-down menu, select **Manage account**. 1. Under **Permissions**, select **Extension access**. 1. In the top right, select **New extension access**. 1. Select **Microsoft Word**. Then, select **Next**. 1. Configure the following fields: + **Name** - A name for your extension is pre-filled for you. You can edit this and enter a descriptive name for the Word extension (maximum 512 alphanumeric characters, hyphens allowed but no spaces). + **Description** (optional) - A description for your extension is pre-filled for you. You can edit this and enter a new description to provide additional context about this extension configuration (maximum 1000 characters). + **M365 tenant ID** - Enter your Microsoft 365 tenant identifier (must be 36 characters). 1. Select **Add** to save the new access configuration. A success message will open up on the top right of your screen. 1. From the success message, select **View extensions** to finish installing your extension. **Note** You can also navigate to the installation screen from **Connections** > **Extensions** in the Amazon Quick menu. Once created, this extension access configuration enables authors and other admin in your organization to create and deploy Amazon Quick extensions within your Microsoft Word environment. **Note** For your end users to begin using your Microsoft Word extension, an admin or author must finish deploying a extension after you configure extension access. Notify your authors that they can view, edit, and complete installation of this extension under **Extensions** in the left navigation once it has been shared. To learn how to do this see [Installing your Microsoft Word extension in the Microsoft Word extension author guide](https://docs.aws.amazon.com/quicksuite/latest/userguide/word-extension-author-guide.html#add-extensions-word). ### Edit Microsoft Word extension access Use these steps to modify the configuration settings of an existing Microsoft Word extension access. 1. Sign in to the Amazon Quick console. 1. In the top right, select the profile picture icon. 1. From the drop-down menu, select **Manage account**. 1. Under **Permissions**, select **Extension access**. 1. Select the three dot menu icon for the **Microsoft Word** extension you need to edit. 1. Select **Edit**. 1. Edit the configuration as required and select **Save** to confirm the changes. Your changes to the Microsoft Word extension access configuration are saved and will take effect immediately. ### Delete Microsoft Word extension access Follow these steps to permanently remove a Microsoft Word extension access configuration. This action cannot be undone. **Note** Deleting a extension access removes access for all users in your M365 tenant and deletes all extensions created for Word. 1. Sign in to the Amazon Quick console. 1. In the top right, select the profile picture icon. 1. From the drop-down menu, select **Manage account**. 1. Under **Permissions**, select **Extension access**. 1. Select the three dot menu icon for the Microsoft Word Extension you need to delete. 1. Select **Delete**. 1. Enter the word, "confirm", and select **DELETE**. **Note** If the process to delete extension access fails, the admin must switch to the author view and delete the Word extensions that are using the configured extension access before returning to delete the extension access. With Microsoft Word extension access configured, your team can now use Amazon Quick to enhance their document creation workflows with AI assistance for reviewing, drafting, revising, and accessing organizational knowledge directly within Word.