Merge pull request #28534 from MicrosoftDocs/main

[AutoPublish] main to live - 05/21 15:31 PDT | 05/22 04:01 IST

Author: Ruchika-mittal01

microsoft-365/admin/manage/idle-session-timeout-web-apps.md

@@ -144,6 +144,10 @@ Azure portal supports a similar inactivity feature, but is tracked in the Azure
 > [!Note]
 > When initially activated within the Azure portal, the timeout duration by default inherits from Microsoft 365 admin center idle session timeout setting. However, the timeout policy for the Azure portal can be explicitly configured within the portal itself.  For more information, see [Azure portal: Signing-Out + Notification](/azure/azure-portal/set-preferences#signing-out--notifications).
 
+### I'm using Microsoft Fabric, how does Idle Session Timeout impact long-running Fabric Notebook executions?
+
+If you are using a non-managed device where Idle Session Timeout is enabled, long-running interactive Fabric Notebook executions may be affected if a user goes inactive beyond the set tenant-wide session timeout policy. This is a pro-active measure to ensure idle devices are not accessible by outside parties. To mitigate, we advise users to not go inactive within M365 web apps while long-running executions are running. 
+
 ### I want to make changes to the idle session timeout policy or delete it. How can I do that?
 
 Update the policy:

microsoft-365/syntex/esignature-overview.md

@@ -73,7 +73,7 @@ The providers facilitate the signing process and send out all relevant notificat
 
 - Tracking of SharePoint eSignature requests through the Approvals app in Microsoft Teams is now available.
 
-- Support for Adobe Acrobat Sign and Docusign is now available worldwide. In the future, there will be potential integration with other electronic signature providers.
+- Support for Adobe Acrobat Sign and DocuSign is now available worldwide. In the future, there will be potential integration with other electronic signature providers.
 
 <br>
 

microsoft-365/syntex/esignature-review-sign-requests.md

@@ -4,7 +4,7 @@ ms.author: chucked
 author: chuckedmonson
 manager: jtremper
 ms.reviewer: amcdonnell
-ms.date: 05/19/2025
+ms.date: 05/21/2025
 audience: enabler
 ms.topic: how-to
 ms.service: microsoft-syntex
@@ -83,9 +83,9 @@ When you have entered all of the required input, select **Submit** to complete t
 
 ![Screenshot of the completed document showing the Submit button.](../media/content-understanding/esignature-submit-dark.png)
 
-The status of the request changes from **In progress** to **Completed**. The document becomes read-only. You'll receive an email notification saying that your signature has been received and the requester will be notified.
+The status of the request changes from **In progress** to **Completed**. The document becomes read-only. You receive an email notification saying that your signature has been received and the requester has been notified.
 
-Once everyone has signed the document, you'll receive an email notification saying where you can view the document and request details. The document is available via the **View request** button in the email for 30 days, so make sure you download it for your own records.
+Once everyone has signed the document, you receive an email notification saying where you can view the document and request details. The document is available via the **View request** button in the email for 30 days, so make sure you download it for your own records.
 
 ### Decline to sign the document
 
@@ -99,9 +99,9 @@ If you review the document and don’t want to sign it, you can decline to sign.
 
     ![Screenshot of the document viewer showing the You're declining to sign screen.](../media/content-understanding/esignature-decline-to-sign-dark.png)
 
-Once you decline, you won't be able to add your signature, but you'll be able to see the document in read-only mode.
+Once you decline, you won't be able to add your signature, but you are able to see the document in read-only mode.
 
-Once you decline, an email notification is sent to the requester saying that you don’t want to sign the document. Declining to sign will complete the signing process and change the status of the request from **In progress** to **Declined**.
+Once you decline, an email notification is sent to the requester saying that you don’t want to sign the document. Declining to sign completes the signing process and changes the status of the request from **In progress** to **Declined**.
 
 If there are more recipients, they'll also receive a notification saying that the request has been declined.
 
@@ -131,27 +131,30 @@ When you create a signature request with SharePoint eSignature, it goes through
 When the status of a request is **Completed**, **Canceled**, or **Declined**, the request can no longer be acted on by either the sender or the recipients. As an example, if a recipient declines a request, the sender would need to send a new request after the reason for declining has been addressed. The original declined request can't be edited.
 
 > [!NOTE]
-> For requests sent via other electronic signature providers, the status reflected is determined by the signature provider and might differ from the status described above.  
+> For requests sent via other electronic signature providers, the status reflected is determined by the signature provider and might differ from the status previously described.  
 
 ## Access the signed document
 
 ### Documents signed with Microsoft SharePoint eSignature
 
 All parties involved in the request receive an email notification saying that the request has been completed and the status of the request is **Completed**. In the email, you can select **View signed document** to access the signed document and the request history.
 
-Signers can continue to access and download the signed document from the email notification for 30 days after receiving the email. Additionally, request senders will be able to access the originating folder in which the signed document was saved directly from the email. The file name of the signed document will be the original file name with "signed" and the date and time appended to it.
+Signers can continue to access and download the signed document from the email notification for 30 days after receiving the email. Additionally, request senders are able to access the originating folder in which the signed document was saved directly from the email. The file name of the signed document will be the original file name with "signed" and the date and time appended to it.
 
 > [!NOTE]
-> When you open a PDF document on a SharePoint site, you won't see the details of the request if your default PDF viewer is set to Adobe. You'll need to set PDF viewer as your default viewer.
+> When you open a PDF document on a SharePoint site, you won't see the details of the request if your default PDF viewer is set to Adobe. You need to set PDF viewer as your default viewer.
 
 #### Security of the signed document
 
-After all recipients have signed the document, the signatures are added and an audit trail is appended to the signed PDF. Details of the request, including activities and timestamps of when they occurred throughout the signing process, are included. The details include the date and time the request created, date and time when the recipients signed, and so on. These details provide evidence of the integrity of the signing process. The signed document is then digitally signed by a Microsoft certificate to ensure that it can't be tampered with.  
+After all recipients sign the document, the signatures are added and an audit trail is appended to the signed PDF. Details of the request, including activities and timestamps of when they occurred throughout the signing process, are included. The details include the date and time the request created, date and time when the recipients signed, and so on. These details provide evidence of the integrity of the signing process. The signed document is then digitally signed by a Microsoft certificate to ensure that it can't be tampered with.  
 
 ### Documents signed with other signature providers
 
-All parties will receive an email notification from the provider when document signing is complete. The email typically contains a link to the signed document or as an attachment. Additionally, a copy of the signed document is automatically stored in SharePoint. Once stored, the creator of the request receives an email from SharePoint eSignature with a link to the SharePoint location. The signed document is stored in a provider specific folder within the SharePoint document library of the original document (the original document is the PDF with which the request was initiated from). The signed document can be found using this folder path: **[Document library] > Apps\Signed documents\provider** (for example, Contoso Documents > Apps > Signed documents > Docusign). The retention policy of the saved document will inherit the retention policy set up by the SharePoint or tenant admin.
-The file name of the signed document will be the original file name with the name of the provider, "signed" and the date and time appended to it.
+All parties receive an email notification from the provider when document signing is complete. The email typically contains a link to the signed document or as an attachment. Additionally, a copy of the signed document is automatically stored in SharePoint. Once stored, the creator of the request receives an email from SharePoint eSignature with a link to the SharePoint location.
+
+The signed document is stored in a provider specific folder within the SharePoint document library of the original document (the original document is the PDF with which the request was initiated from). The signed document can be found using this folder path: **[Document library] > Apps\Signed documents\provider** (for example, Contoso Documents > Apps > Signed documents > DocuSign). The retention policy of the saved document inherits the retention policy set up by the SharePoint or tenant admin.
+
+The file name of the signed document will be the original file name with the name of the provider, with "signed" and the date and time appended to it.
 
 > [!NOTE]
-> A copy of the signed document will not be saved if the request is declined or canceled. Any additional document uploaded via a provider outside of SharePoint while creating a request will also not be saved back to SharePoint. Only documents initiated from SharePoint are saved back to SharePoint.  
+> A copy of the signed document won't be saved if the request is declined or canceled. Any other document uploaded via a provider outside of SharePoint while creating a request will also not be saved back to SharePoint. Only documents initiated from SharePoint are saved back to SharePoint.