![]() Quick Assist starts RDP control and connects to the RDP Relay service. The sharer is prompted to confirm allowing the helper to share their desktop with the helper. The helper is prompted to select View Only or Full Control. The sharer's Quick Assist instance joins the RCC chat session. The helper then provides the code to the sharer.Īfter the sharer enters the code in their Quick Assist app, Quick Assist uses that code to contact the Remote Assistance Service and join that specific session. An RCC chat session is established, and the helper's Quick Assist instance joins it. Quick Assist on the helper's side contacts the Remote Assistance Service to obtain a session code. ![]() The helper selects Assist another person. Required diagnostic data for client and services used by Quick Assist.īoth the helper and the sharer start Quick Assist. Primary endpoint used for Quick Assist application *.Īzure Communication Services (ACS) technology the Quick Assist app uses. Required for logging in to the application (Microsoft account)Īzure Communication Service for chat and connection between parties. Used for chat services within Quick Assist Required for chat services within Quick Assist Used for accessibility features within the appĪzure Communication Service for chat and connection between parties ![]() The traffic is encrypted with TLS 1.2.īoth the helper and sharer must be able to reach these endpoints over port 443: Domain/Name Quick Assist communicates over port 443 (https) and connects to the Remote Assistance Service at by using the Remote Desktop Protocol (RDP). Local Active Directory authentication isn't currently supported. The helper can authenticate when they sign in by using a Microsoft account (MSA) or Azure Active Directory (Azure AD). In case the helper and sharer use different keyboard layouts or mouse settings, the ones from the sharer are used during the session.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |