Merge branch 'main' into MandiOhlinger-patch-1

Author: MandiOhlinger

microsoft-365/solutions/collaborate-guests-cross-cloud.md

@@ -40,8 +40,9 @@ In order to invite guests from an organization in a different Microsoft Azure cl
 Note that tenants in Microsoft Azure Government (Microsoft 365 GCC High and DoD) can't create a cross-tenant connection with tenants in Microsoft Azure China.
 
 > [!NOTE]
-> VDI clients aren't supported for cross-cloud guests.
-> 
+> VDI clients using the new [SlimCore-based optimization](/microsoftteams/vdi-2#cross-cloud-collaboration) are supported for cross-cloud meetings. WebRTC-based optimization doesn't support cross-cloud meetings.
+
+> [!NOTE]
 > B2B Member accounts aren't supported for cross cloud guests.  All cross cloud users must be of type B2B guest.
 
 > [!IMPORTANT]

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

@@ -135,7 +135,7 @@ When the status of a request is **Completed**, **Canceled**, or **Declined**, th
 
 ## 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.  
+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.
 
 > [!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.
@@ -148,4 +148,4 @@ After all recipients have signed the document, the signatures are added and an a
 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.
 
 > [!NOTE]
-> A copy of the signed document will not be saved if the request is declined or canceled. Any additional document uploaded via the third party platform (i.e. 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 will not be saved if the request is declined or canceled. Any additional document uploaded via the third party platform (i.e. 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.  

microsoft-365/syntex/solutions/agreements-expirations.md

@@ -4,7 +4,7 @@ ms.author: chucked
 author: chuckedmonson
 manager: jtremper
 ms.reviewer: vbarla
-ms.date: 04/10/2025
+ms.date: 05/19/2025
 audience: admin
 ms.topic: conceptual
 ms.service: microsoft-syntex
@@ -44,11 +44,11 @@ If the **Expiration date** isn't included in the agreement, it's treated as an e
 
 When the **Expiration date** field is filled in the agreement, the following actions occur:
 
-**Two months before the expiration date:**
+**Three months before the expiration date:**
 
 - A reminder notification is sent to the [default recipients](#default-recipients-of-notifications), indicating the specific date the agreement will expire.
 
-- This notification is sent weekly for the two months leading up to the expiration date.
+- This notification is sent weekly for the three months leading up to the expiration date.
 
 **On the expiration date:**