Merge pull request #28311 from MicrosoftDocs/main

[AutoPublish] main to live - 04/24 10:29 PDT | 04/24 22:59 IST

Author: Ruchika-mittal01

copilot/multiple-account-access.md

@@ -13,7 +13,7 @@ ms.collection:
 - m365copilot
 - magic-ai-copilot
 hideEdit: true
-ms.date: 04/23/2025
+ms.date: 04/24/2025
 ---
 
 # Multiple account access to Copilot for work and school documents
@@ -72,7 +72,7 @@ The end-user experience for blocked users viewing work and school documents is a
 
 ## Apps where multiple account access to Copilot is available
 
-As of April 23, 2025, multiple account access is rolling out gradually in the following apps, starting with the version listed.
+As of April 24, 2025, multiple account access is rolling out gradually in the following apps, starting with the version listed.
 
 ### On Android devices
 
@@ -92,9 +92,11 @@ As of April 23, 2025, multiple account access is rolling out gradually in the fo
 
 ### On iPad devices
 
+- Excel: Version 2.95.224.0
 - PowerPoint: Version 2.95.224.0
 
 ### On Windows devices
 
+- Excel: Version 2503
 - PowerPoint: Version 2503
 - Word: Version 2503

microsoft-365/syntex/esignature-troubleshoot.md

@@ -4,7 +4,7 @@ ms.author: chucked
 author: chuckedmonson
 manager: jtremper
 ms.reviewer: amcdonnell
-ms.date: 04/15/2025
+ms.date: 04/24/2025
 audience: enabler
 ms.topic: troubleshooting-general
 ms.service: microsoft-syntex
@@ -21,18 +21,18 @@ description: Learn how to troubleshoot issues with sending, receiving, or viewin
 
 ## Unable to create a request
 
-If you aren't able to create a signature request, make sure that you have edit rights to the folder containing the document to be signed and that the PDF doesn't exceed 10 MB in size. If the document is stored in a private group, the signers must be members of the private group to recieve the request. You can also check the PDF viewer settings, the collaboration settings, or the access policies below. Refer to the [setup page](/microsoft-365/syntex/esignature-setup) to ensure the correct settings are done. Also, check that the PDF you're attempting to sign isn't already electronically signed using SharePoint eSignature or any other electronic signature provider.
+If you can't create a signature request, ensure you have edit rights to the folder containing the document and that the PDF is under 10 MB. If the document is stored in a private group, the signers must be members of the private group to receive the request. You can also check the PDF viewer settings, the collaboration settings, or the access policies. Refer to [Admin setup](esignature-setup.md) to ensure the correct settings are done. Also, check that the PDF you're attempting to sign isn't already electronically signed using SharePoint eSignature or any other electronic signature provider.
 
 > [!NOTE]
-> New eSignature requests can't be started from documents that have been previously signed. You need to choose another document to create the request.
+> New eSignature requests can't be started from documents that were previously signed. You need to choose another document to create the request.
 
 ### Default program for PDF viewing
 
-The PDF viewer is opened by selecting a PDF file from a SharePoint library. The ability to use the **Get signatures** option won't be available if the PDF is viewed in any other way, for example, in Microsoft Edge or Adobe Reader.
+The PDF viewer is opened by selecting a PDF file from a SharePoint library. The ability to use the **Get signatures** option isn't available if the PDF is viewed in any other way, for example, in Microsoft Edge or Adobe Reader.
 
 ### Collaboration settings
 
-SharePoint eSignature is an extension of SharePoint document storage and management service. Existing access, sharing, and data loss prevention policies that are already applied at the tenant level, SharePoint site and library level, or folder and file level might affect whether a request can be started from a document in SharePoint and who it can be sent to. Some of the scenarios that might affect the signature request process are:
+SharePoint eSignature is an extension of SharePoint document storage and management service. Existing access, sharing, and data loss prevention policies at the tenant, SharePoint site, library, folder, or file level might affect whether a request can be started from a document in SharePoint and who it can be sent to. Some of the scenarios that might affect the signature request process are:
 
 - If encryption is applied (for example, sensitivity labeling applied to the file), the ability to view the document wouldn't be available from SharePoint and therefore can't start a Signature request from there. Read more about [sensitivity labels](/purview/sensitivity-labels).
 
@@ -48,9 +48,11 @@ Connect-SPOService -Url "https://yourtenant.sharepoint.com"
 Get-SPOSite -Limit All | Select-Object Url, SharingCapability
 ~~~
 
-### Conditional access policies
+### Unable to send a request to an external recipient
 
-Certain [conditional access](/entra/identity/conditional-access/overview) policies might determine whether an external recipient (signers outside of your organization or Microsoft 365 tenant) is able sign a document. When this happens, the external signers might not be able to access the document for signing. In some other cases, they might be able to access the document for signing but the signing operation is unsuccessful. One common way to resolve this is to contact your IT admin who will be able to add the SharePoint eSignature app to the list of approved apps via the  Microsoft Entra admin center.
+Your IT admin might not have configured Microsoft Entra B2B to allow new external guests. Review the [External recipients](esignature-setup.md#external-recipients) section in [Admin setup](esignature-setup.md) to determine if this meets your compliance and security requirements when enabling eSignature.
+
+Certain [conditional access](/entra/identity/conditional-access/overview) policies might determine whether an external recipient (signers outside of your organization or Microsoft 365 tenant) is able sign a document. When this happens, the external signers might not be able to access the document for signing. In some other cases, they might be able to access the document for signing but the signing operation is unsuccessful. One common way to resolve this is to contact your IT admin who can add the SharePoint eSignature app to the list of approved apps via the Microsoft Entra admin center.
 
 In some cases, the admin might need to add the SharePoint eSignature app (formally called Microsoft eSign service) to the **Excluded Apps** list in the **Conditional Access policy** > **Target resources** section so that the policy doesn't apply to the SharePoint eSignature app. The admin can verify the changes using the WhatIf tool with the policy.
 
@@ -60,15 +62,15 @@ When you initiate a signature request from a document for another provider, such
 
 ## Unable to find the request emails
 
-If you were sent an eSignature request and can't find it in your email inbox, you should check your spam or junk folder. It's also good practice to mark the sender as non-spam so that future emails from the same sender go directly into your inbox.
+If you can't find an eSignature request in your email inbox, check your spam or junk folder. It's also good practice to mark the sender as safe so that future emails from the same sender go directly into your inbox.
 
 ## Unable to sign a document as an external recipient
 
-When you receive a document for signing from someone outside of your organization, you might be able to access and read the document but the signing operation fails when you attempt to sign it. Other times, you might not be able to access and read the document. If you're experiencing any issues with signing a document sent from someone outside your organization, contact the sender who will be able to resolve the issue.
+When you receive a document for signing from someone outside of your organization, you might be able to access and read the document but the signing operation fails when you attempt to sign it. Other times, you might not be able to access and read the document. If you're experiencing any issues with signing a document sent from someone outside your organization, contact the sender who can resolve the issue.
 
 ## Unable to access a signed document
 
-Before a signature request is sent and at the completion of the request, certain checks are done to ensure that the sender has the permissions to write to the document and the originating folder because the final signed document is saved in this folder. If the sender loses access to this folder at any point before signing is complete, they might not be able to access the signed document permanently. In this scenario, the sender is provided temporary access of 30 days to the signed document through the completion email. To access the folder and document, the sender should ensure that they have read permission to the originating folder or request access from the owner.
+Before sending a signature request and upon its completion, checks are performed to ensure the sender has permission to write to the document and the originating folder, as the final signed document will be saved in this folder. If the sender loses access to this folder at any point before signing is complete, they might not be able to access the signed document permanently. In this scenario, the sender is provided temporary access of 30 days to the signed document through the completion email. To access the folder and document, the sender should ensure that they have read permission to the originating folder or request access from the owner.
 
 Additionally, the eSignature service might not be able to save a copy of the signed document to the originating folder if the folder was accidentally deleted before the signature request was completed.