Merge pull request #213554 from petrsvihlik/patch-6

Sign-out best practices

Author: prmerger-automator[bot]

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

@@ -282,9 +282,11 @@ leaveChatBtn.addEventListener('click', function() {
 });
 ```
 
+If you want to cancel subsequent refresh tasks, [dispose](#clean-up-resources) of the Credential object.
+
 ### Clean up resources
 
-Since the Credential object can be passed to multiple Chat or Calling client instances, the SDK will make no assumptions about its lifetime and leaves the responsibility of its disposal to the developer. It's up to the Communication Services applications to dispose the Credential instance when it's no longer needed. Disposing the credential is also the recommended way of canceling scheduled refresh actions when the proactive refreshing is enabled.
+Since the Credential object can be passed to multiple Chat or Calling client instances, the SDK will make no assumptions about its lifetime and leaves the responsibility of its disposal to the developer. It's up to the Communication Services applications to dispose the Credential instance when it's no longer needed. Disposing the credential will also cancel scheduled refresh actions when the proactive refreshing is enabled.
 
 Call the `.dispose()` function.
 
@@ -296,6 +298,13 @@ const chatClient = new ChatClient("<endpoint-url>", tokenCredential);
 tokenCredential.dispose()
 ```
 
+## Handle a sign-out
+
+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](#clean-up-resources) of the Credential object.
+- To sign a user out from multiple services, implement a signaling mechanism to notify all services to [dispose](#clean-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.
+
 ---
 
 ## Next steps