Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into patricka-merge-dev-tutorials

Author: PatAltimore

articles/active-directory/develop/access-tokens.md

@@ -16,18 +16,18 @@ The UI Library now gives developers the ability to provide a more customized exp
 
 #### Local Options
 
-`LocalOptions` is data model that consists of `ParticipantViewData` and `SetupScreenViewData`.  By default for `ParticipantViewData`, the UI library will display the `displayName` injected in `RemoteOptions` that is sent to Azure Communication Service backend server. If `ParticipantViewData` is injected, the participant `displayName` and `avatar` will be displayed in all avatar components. 
+`LocalOptions` is data model that consists of `ParticipantViewData` and `SetupScreenViewData`.  By default for `ParticipantViewData`, the UI library displays the `displayName` injected in `RemoteOptions` that is sent to Azure Communication Service backend server. If `ParticipantViewData` is injected, the participant `displayName` and `avatar` will be displayed in all avatar components. 
 
-Similarly, for 'SetupScreenViewData', by default the UI library will display 'Setup' as the title and subtitle will be set to hidden. The `title` and `subtitle` in 'SetupScreenViewData' would overwrite the navigation bar's title and subtitle in pre-meeting screen respectively. 
+Similarly, for 'SetupScreenViewData', by default the UI library displays 'Setup' as the title and subtitle is set to hidden. The `title` and `subtitle` in 'SetupScreenViewData' would overwrite the navigation bar's title and subtitle in pre-meeting screen respectively. 
 
 #### Participant View Data
 
 `ParticipantViewData` is an object that sets the `displayName` and `avatar` UIImage for avatar components. This class is injected into the UI Library to set avatar information, and it will always be locally stored and never sent up to the server.
 
 #### Setup Screen View Data
 
-`SetupScreenViewData` is an object that sets the `title` and `subtitle` for the navigationBar on pre-meeting screen (aka. Setup View). If `SetupScreenViewData` is defined, then 'title' must be provided as it's a required field. 'subtitle', however, is not required. 
-If `subtitle` is not defined, then the subtitle would always be set to hidden. This class is locally stored and its information will not be sent up to the server.
+`SetupScreenViewData` is an object that sets the `title` and `subtitle` for the navigationBar on pre-meeting screen (also known as Setup View). If `SetupScreenViewData` is defined, then 'title' must be provided as it's a required field. 'subtitle', however, isn't required. 
+If `subtitle` isn't defined, then the subtitle would always be set to hidden. This class is locally stored and its information won't be sent up to the server.
 
 #### Usage
 
@@ -60,12 +60,12 @@ On remote participant join, developers can inject the participant view data for
 To set the participant view data for remote participant, set `onRemoteParticipantJoined` completion for events handler. On remote participant join, use `CallComposite` `set(remoteParticipantViewData:, for:, completionHandler:)` to inject view data for remote participant. The participant identifier `CommunicationIdentifier` is used to uniquely identify a remote participant. The optional completion handler is used for returning result of the set operation.
 
 ```swift
-callComposite.events.onRemoteParticipantJoined = { identifiers in
+callComposite.events.onRemoteParticipantJoined = { [weak callComposite] identifiers in
   for identifier in identifiers {
     // map identifier to displayName
     let participantViewData = ParticipantViewData(displayName: "<DISPLAY_NAME>")
-    callComposite.set(remoteParticipantViewData: participantViewData,
-                      for: identifier) { result in
+    callComposite?.set(remoteParticipantViewData: participantViewData,
+                       for: identifier) { result in
       switch result {
       case .success:
         print("Set participant view data succeeded")

articles/communication-services/how-tos/ui-library-sdk/includes/data-model/ios.md

@@ -49,13 +49,13 @@ In Xcode, create a new project:
 
     target 'UILibraryQuickStart' do
         use_frameworks!
-        pod 'AzureCommunicationUIChat', '1.0.0-beta2'
+        pod 'AzureCommunicationUIChat', '1.0.0-beta.3'
     end
     ```
 
 1. Run `pod install --repo-update`.
 
-1. In Xcode, open the generated *.xcworkspace* file.
+1. In Xcode, open the generated *xcworkspace* file.
 
 ### Turn off Bitcode
 

articles/communication-services/quickstarts/ui-library/includes/get-started-chat/ios.md

@@ -715,6 +715,10 @@ The only operation possible when the encryption key has been revoked is account
 
 ### Assign a new managed-identity to the restored database account to continue accessing or recover access to the database account
 
+User-Assigned Identity is tied to a specified Cosmos DB account, whenever we assign a User-Assigned Identity to an account, ARM forwards the request to managed service identities to make this connection. Currently we carry over user-identity information from the source database account to the target database account during the restore (for both Continuous and Periodic backup restore) of CMK + User-Assigned Identity,  
+ 
+Since the identity metadata is bound with the source database account and restore workflow doesn't re-scope identity to the target database account. This will cause the restored database accounts to be in a bad state, and become inaccessible after the source account is deleted and identity’s renew time is expired. 
+
 Steps to assign a new managed-identity:
 1. [Create a new user-assigned managed identity.](../active-directory/managed-identities-azure-resources/how-manage-user-assigned-managed-identities.md#create-a-user-assigned-managed-identity)
 2. [Grant KeyVault key access to this identity.](#choosing-the-preferred-security-model)