Merge pull request #223701 from ddematheu2/patch-44

Update access-tokens.md

Author: v-shils

articles/communication-services/.openpublishing.redirection.communication-services.json

@@ -134,10 +134,30 @@
         "redirect_url": "/azure/communication-services/concepts/call-automation/call-automation",
         "redirect_document_id": false
       },
+      {
+        "source_path_from_root": "/articles/communication-services/quickstarts/identity/quick-create-identity.md",
+        "redirect_url": "/azure/communication-services/quickstarts/identity/access-tokens",
+        "redirect_document_id": false
+      },
+      {
+        "source_path_from_root": "/articles/communication-services/quickstarts/identity/logic-app.md",
+        "redirect_url": "/azure/communication-services/quickstarts/identity/access-tokens",
+        "redirect_document_id": false
+      },
+      {
+        "source_path_from_root": "/articles/communication-services/quickstarts/access-tokens.md",
+        "redirect_url": "/azure/communication-services/quickstarts/identity/access-tokens",
+        "redirect_document_id": false
+      },
       {
         "source_path_from_root": "/articles/communication-services/quickstarts/identity/service-principal-from-cli.md",
         "redirect_url": "/azure/communication-services/quickstarts/identity/service-principal",
         "redirect_document_id": false
+      },
+      {
+        "source_path_from_root": "/articles/communication-services/quickstarts/identity/access-token-teams-external-users.md",
+        "redirect_url": "/azure/communication-services/quickstarts/identity/access-tokens",
+        "redirect_document_id": false
       }
     ]
 }

articles/communication-services/concepts/authentication.md

@@ -37,7 +37,7 @@ Each authorization option is briefly described below:
 
 ### Access Key
 
-Access key authentication is suitable for service applications running in a trusted service environment. Your access key can be found in the Azure Communication Services portal. The service application uses it as a credential to initialize the corresponding SDKs. See an example of how it is used in the [Identity SDK](../quickstarts/access-tokens.md). 
+Access key authentication is suitable for service applications running in a trusted service environment. Your access key can be found in the Azure Communication Services portal. The service application uses it as a credential to initialize the corresponding SDKs. See an example of how it is used in the [Identity SDK](../quickstarts/identity/access-tokens.md). 
 
 Since the access key is part of the connection string of your resource, authentication with a connection string is equivalent to authentication with an access key.
 
@@ -55,7 +55,7 @@ Use our [Trusted authentication service hero sample](../samples/trusted-auth-sam
 
 ### User Access Tokens
 
-User access tokens are generated using the Identity SDK and are associated with users created in the Identity SDK. See an example of how to [create users and generate tokens](../quickstarts/access-tokens.md). Then, user access tokens are used to authenticate participants added to conversations in the Chat or Calling SDK. For more information, see [add chat to your app](../quickstarts/chat/get-started.md). User access token authentication is different compared to access key and Azure AD authentication in that it is used to authenticate a user rather than a secured Azure resource.
+User access tokens are generated using the Identity SDK and are associated with users created in the Identity SDK. See an example of how to [create users and generate tokens](../quickstarts/identity/access-tokens.md). Then, user access tokens are used to authenticate participants added to conversations in the Chat or Calling SDK. For more information, see [add chat to your app](../quickstarts/chat/get-started.md). User access token authentication is different compared to access key and Azure AD authentication in that it is used to authenticate a user rather than a secured Azure resource.
 
 ## Using identity for monitoring and metrics
 
@@ -70,7 +70,7 @@ The user identity is intended to act as a primary key for logs and metrics colle
 > [Create an Azure Active Directory service principal application from the Azure CLI](../quickstarts/identity/service-principal.md?pivots=platform-azcli)
 
 > [!div class="nextstepaction"]
-> [Create user access tokens](../quickstarts/access-tokens.md)
+> [Create user access tokens](../quickstarts/identity/access-tokens.md)
 
 > [!div class="nextstepaction"]
 > [Trusted authentication service hero sample](../samples/trusted-auth-sample.md)

articles/communication-services/concepts/chat/concepts.md

@@ -55,7 +55,7 @@ There are two core parts to chat architecture: 1) Trusted Service and 2) Client
 
 :::image type="content" source="../../media/chat-architecture.svg" alt-text="Diagram showing Communication Services' chat architecture.":::
 
- - **Trusted service:** To properly manage a chat session, you need a service that helps you connect to Communication Services by using your resource connection string. This service is responsible for creating chat threads, adding and removing participants, and issuing access tokens to users. More information about access tokens can be found in our [access tokens](../../quickstarts/access-tokens.md) quickstart.
+ - **Trusted service:** To properly manage a chat session, you need a service that helps you connect to Communication Services by using your resource connection string. This service is responsible for creating chat threads, adding and removing participants, and issuing access tokens to users. More information about access tokens can be found in our [access tokens](../../quickstarts/identity/access-tokens.md) quickstart.
  - **Client app:**  The client application connects to your trusted service and receives the access tokens that are used by users to connect directly to Communication Services. After creating the chat thread and adding users as participants, they can use the client application to connect to the chat thread and send messages. Use real-time notifications feature, which we discuss below, in your client application to subscribe to message & thread updates from other participants.
 
 

articles/communication-services/concepts/credentials-best-practices.md

@@ -303,7 +303,7 @@ tokenCredential.dispose()
 Depending on your scenario, you may want to sign a user out from one or more services:
 
 - To sign a user out from a single service, [dispose](#cleaning-up-resources) of the Credential object.
-- To sign a user out from multiple services, implement a signaling mechanism to notify all services to [dispose](#cleaning-up-resources) of the Credential object, and additionally, [revoke all access tokens](../quickstarts/access-tokens.md?tabs=windows&pivots=programming-language-javascript#revoke-access-tokens) for a given identity.
+- To sign a user out from multiple services, implement a signaling mechanism to notify all services to [dispose](#cleaning-up-resources) of the Credential object, and additionally, [revoke all access tokens](../quickstarts/identity/access-tokens.md?tabs=windows&pivots=programming-language-javascript#revoke-access-tokens) for a given identity.
 
 ---
 
@@ -318,5 +318,5 @@ In this article, you learned how to:
 
 To learn more, you may want to explore the following quickstart guides:
 
-* [Create and manage access tokens](../quickstarts/access-tokens.md)
+* [Create and manage access tokens](../quickstarts/identity/access-tokens.md)
 * [Manage access tokens for Teams users](../quickstarts/manage-teams-identity.md)

articles/communication-services/concepts/identity-model.md

@@ -82,7 +82,7 @@ If you cache access tokens to a backing store, we recommend using encryption. An
 
 ## Next steps
 
-* For an introduction to access token management, see [Create and manage access tokens](../quickstarts/access-tokens.md).
+* For an introduction to access token management, see [Create and manage access tokens](../quickstarts/identity/access-tokens.md).
 * For an introduction to authentication, see [Authenticate to Azure Communication Services](./authentication.md).
 * For an introduction to data residency and privacy, see [Region availability and data residency](./privacy.md).
 * To learn how to quickly create identities for testing, see the [quick-create identity quickstart](../quickstarts/identity/quick-create-identity.md).

articles/communication-services/concepts/includes/identifiers/identifiers-android.md

@@ -15,7 +15,7 @@ ms.author: domessin
 
 ### Communication user
 
-The `CommunicationUserIdentifier` represents a user identity that was created using the [Identity SDK or REST API](../../../quickstarts/access-tokens.md). It's the only identifier used if your application doesn't use Microsoft Teams interoperability or Telephony features.
+The `CommunicationUserIdentifier` represents a user identity that was created using the [Identity SDK or REST API](../../../quickstarts/identity/access-tokens.md). It's the only identifier used if your application doesn't use Microsoft Teams interoperability or Telephony features.
 
 
 #### Basic usage

articles/communication-services/concepts/includes/identifiers/identifiers-ios.md

@@ -15,7 +15,7 @@ ms.author: domessin
 
 ### Communication user
 
-The `CommunicationUserIdentifier` represents a user identity that was created using the [Identity SDK or REST API](../../../quickstarts/access-tokens.md). It's the only identifier used if your application doesn't use Microsoft Teams interoperability or Telephony features.
+The `CommunicationUserIdentifier` represents a user identity that was created using the [Identity SDK or REST API](../../../quickstarts/identity/access-tokens.md). It's the only identifier used if your application doesn't use Microsoft Teams interoperability or Telephony features.
 
 
 #### Basic usage

articles/communication-services/concepts/includes/identifiers/identifiers-java.md

@@ -15,7 +15,7 @@ ms.author: domessin
 
 ### Communication user
 
-The `CommunicationUserIdentifier` represents a user identity that was created using the [Identity SDK or REST API](../../../quickstarts/access-tokens.md). It's the only identifier used if your application doesn't use Microsoft Teams interoperability or Telephony features.
+The `CommunicationUserIdentifier` represents a user identity that was created using the [Identity SDK or REST API](../../../quickstarts/identity/access-tokens.md). It's the only identifier used if your application doesn't use Microsoft Teams interoperability or Telephony features.
 
 
 #### Basic usage

articles/communication-services/concepts/includes/identifiers/identifiers-js.md

@@ -15,7 +15,7 @@ ms.author: domessin
 
 ### Communication user
 
-The `CommunicationUserIdentifier` interface represents a user identity that was created using the [Identity SDK or REST API](../../../quickstarts/access-tokens.md). It's the only identifier used if your application doesn't use Microsoft Teams interoperability or Telephony features.
+The `CommunicationUserIdentifier` interface represents a user identity that was created using the [Identity SDK or REST API](../../../quickstarts/identity/access-tokens.md). It's the only identifier used if your application doesn't use Microsoft Teams interoperability or Telephony features.
 
 
 #### Basic usage

articles/communication-services/concepts/includes/identifiers/identifiers-net.md

@@ -15,7 +15,7 @@ ms.author: domessin
 
 ### Communication user
 
-The `CommunicationUserIdentifier` represents a user identity that was created using the [Identity SDK or REST API](../../../quickstarts/access-tokens.md). It's the only identifier used if your application doesn't use Microsoft Teams interoperability or Telephony features.
+The `CommunicationUserIdentifier` represents a user identity that was created using the [Identity SDK or REST API](../../../quickstarts/identity/access-tokens.md). It's the only identifier used if your application doesn't use Microsoft Teams interoperability or Telephony features.
 
 
 #### Basic usage