Skip to content

Commit 60f0cc2

Browse files
authored
Merge branch 'main' into daisyfell-collab-metadata
2 parents 11dcc99 + 7715f7e commit 60f0cc2

4 files changed

Lines changed: 22 additions & 20 deletions

File tree

copilot/microsoft-365-copilot-setup.md

Lines changed: 7 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ f1.keywords:
55
ms.author: camillepack
66
author: camillepack
77
manager: scotv
8-
ms.date: 05/15/2025
8+
ms.date: 05/19/2025
99
audience: Admin
1010
ms.topic: get-started
1111
ms.service: microsoft-365-copilot
@@ -32,25 +32,21 @@ This article provides guidance for administrators on preparing their organizatio
3232

3333
## Prerequisites
3434

35-
- This article uses the following admin centers. These admin centers require a specific role to complete the tasks in the article.
35+
- This article uses the following admin centers. These **admin centers require a specific role** to complete the tasks in the article.
3636

3737
- **[Microsoft 365 admin center](https://admin.microsoft.com)**: There are different roles depending on the task you need to complete. To learn more about roles, see [Commonly used Microsoft 365 admin center roles](/microsoft-365/admin/add-users/about-admin-roles#commonly-used-microsoft-365-admin-center-roles).
3838
- **[SharePoint admin center](https://go.microsoft.com/fwlink/?linkid=2185219)**: Sign in as the [SharePoint administrator](/sharepoint/sharepoint-admin-role).
3939
- **[Microsoft Purview portal](https://purview.microsoft.com)**: There are different roles depending on the task you need to complete. To learn more, see:
4040
- [Permissions required to create and manage sensitivity labels](/purview/get-started-with-sensitivity-labels#permissions-required-to-create-and-manage-sensitivity-labels)
4141
- [Roles and role groups in Microsoft Defender for Office 365 and Microsoft Purview](/defender-office-365/scc-permissions)
4242

43-
- Make sure you:
43+
- Make sure you have an appropriate **subscription plan to purchase Microsoft 365 Copilot**. Microsoft 365 Copilot licenses are available as an add-on to other licensing plans. To learn more, see [Microsoft 365 Copilot license options](microsoft-365-copilot-licensing.md).
4444

45-
- Have an appropriate subscription plan to purchase Microsoft 365 Copilot
45+
You can purchase Microsoft 365 Copilot licenses through the [Microsoft 365 admin center](https://admin.microsoft.com) (**Billing** > **Purchase services**), Microsoft partners, or your Microsoft account team.
4646

47-
Microsoft 365 Copilot licenses are available as an add-on to other licensing plans. To learn more, see [Microsoft 365 Copilot license options](microsoft-365-copilot-licensing.md).
47+
More licenses might be required to use some of the features describes in this article, like [Microsoft Purview](/office365/servicedescriptions/microsoft-365-service-descriptions/microsoft-365-tenantlevel-services-licensing-guidance/microsoft-purview-service-description) and [Microsoft SharePoint Premium - SharePoint Advanced Management overview](/sharepoint/advanced-management#licensing).
4848

49-
You can purchase Microsoft 365 Copilot licenses through the [Microsoft 365 admin center](https://admin.microsoft.com) (**Billing** > **Purchase services**), Microsoft partners, or your Microsoft account team.
50-
51-
More licenses might be required to use some of the features describes in this article, like [Microsoft Purview](/office365/servicedescriptions/microsoft-365-service-descriptions/microsoft-365-tenantlevel-services-licensing-guidance/microsoft-purview-service-description) and [Microsoft SharePoint Premium - SharePoint Advanced Management overview](/sharepoint/advanced-management#licensing).
52-
53-
- Configure the [Microsoft 365 app and network requirements for Microsoft 365 Copilot](microsoft-365-copilot-requirements.md).
49+
- Step through and **configure the [Microsoft 365 app and network requirements for Microsoft 365 Copilot](microsoft-365-copilot-requirements.md)**.
5450

5551
## Readiness activities
5652

@@ -168,7 +164,7 @@ With the Copilot Control System, you can:
168164
- Configure plugins and permissions
169165
- Enable the use of web data as grounding data in Copilot
170166

171-
To learn more, see [Manage Microsoft 365 Copilot settings](microsoft-365-copilot-page.md).
167+
To learn more, see [Manage Microsoft 365 Copilot scenarios](microsoft-365-copilot-page.md) and [configure the Microsoft 365 Copilot app](microsoft-365-copilot-app-admin-settings.md).
172168

173169
### Step 4 - Deploy to some users and measure adoption
174170

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

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -41,8 +41,9 @@ In order to invite guests from an organization in a different Microsoft Azure cl
4141
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.
4242

4343
> [!NOTE]
44-
> VDI clients aren't supported for cross-cloud guests.
45-
>
44+
> 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.
45+
46+
> [!NOTE]
4647
> B2B Member accounts aren't supported for cross cloud guests. All cross cloud users must be of type B2B guest.
4748
4849
> [!IMPORTANT]

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

Lines changed: 9 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ ms.author: chucked
44
author: chuckedmonson
55
manager: jtremper
66
ms.reviewer: amcdonnell
7-
ms.date: 05/06/2025
7+
ms.date: 05/19/2025
88
audience: enabler
99
ms.topic: how-to
1010
ms.service: microsoft-syntex
@@ -134,8 +134,12 @@ When the status of a request is **Completed**, **Canceled**, or **Declined**, th
134134
> 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.
135135
136136
## Access the signed document
137+
137138
### Documents signed with Microsoft SharePoint eSignature
138-
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.
139+
140+
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.
141+
142+
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.
139143

140144
> [!NOTE]
141145
> 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.
@@ -145,7 +149,8 @@ All parties involved in the request receive an email notification saying that th
145149
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.
146150

147151
### Documents signed with other signature providers
148-
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.
152+
153+
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.
149154

150155
> [!NOTE]
151-
> 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.
156+
> 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.

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ ms.author: chucked
44
author: chuckedmonson
55
manager: jtremper
66
ms.reviewer: vbarla
7-
ms.date: 04/10/2025
7+
ms.date: 05/19/2025
88
audience: admin
99
ms.topic: conceptual
1010
ms.service: microsoft-syntex
@@ -44,11 +44,11 @@ If the **Expiration date** isn't included in the agreement, it's treated as an e
4444

4545
When the **Expiration date** field is filled in the agreement, the following actions occur:
4646

47-
**Two months before the expiration date:**
47+
**Three months before the expiration date:**
4848

4949
- A reminder notification is sent to the [default recipients](#default-recipients-of-notifications), indicating the specific date the agreement will expire.
5050

51-
- This notification is sent weekly for the two months leading up to the expiration date.
51+
- This notification is sent weekly for the three months leading up to the expiration date.
5252

5353
**On the expiration date:**
5454

0 commit comments

Comments
 (0)