You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: copilot/microsoft-365-copilot-setup.md
+7-11Lines changed: 7 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ f1.keywords:
5
5
ms.author: camillepack
6
6
author: camillepack
7
7
manager: scotv
8
-
ms.date: 05/15/2025
8
+
ms.date: 05/19/2025
9
9
audience: Admin
10
10
ms.topic: get-started
11
11
ms.service: microsoft-365-copilot
@@ -32,25 +32,21 @@ This article provides guidance for administrators on preparing their organizatio
32
32
33
33
## Prerequisites
34
34
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.
36
36
37
37
-**[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).
38
38
-**[SharePoint admin center](https://go.microsoft.com/fwlink/?linkid=2185219)**: Sign in as the [SharePoint administrator](/sharepoint/sharepoint-admin-role).
39
39
-**[Microsoft Purview portal](https://purview.microsoft.com)**: There are different roles depending on the task you need to complete. To learn more, see:
40
40
-[Permissions required to create and manage sensitivity labels](/purview/get-started-with-sensitivity-labels#permissions-required-to-create-and-manage-sensitivity-labels)
41
41
-[Roles and role groups in Microsoft Defender for Office 365 and Microsoft Purview](/defender-office-365/scc-permissions)
42
42
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).
44
44
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.
46
46
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).
48
48
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)**.
54
50
55
51
## Readiness activities
56
52
@@ -168,7 +164,7 @@ With the Copilot Control System, you can:
168
164
- Configure plugins and permissions
169
165
- Enable the use of web data as grounding data in Copilot
170
166
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).
172
168
173
169
### Step 4 - Deploy to some users and measure adoption
Copy file name to clipboardExpand all lines: microsoft-365/solutions/collaborate-guests-cross-cloud.md
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -41,8 +41,9 @@ In order to invite guests from an organization in a different Microsoft Azure cl
41
41
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.
42
42
43
43
> [!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]
46
47
> B2B Member accounts aren't supported for cross cloud guests. All cross cloud users must be of type B2B guest.
Copy file name to clipboardExpand all lines: microsoft-365/syntex/esignature-review-sign-requests.md
+9-4Lines changed: 9 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ ms.author: chucked
4
4
author: chuckedmonson
5
5
manager: jtremper
6
6
ms.reviewer: amcdonnell
7
-
ms.date: 05/06/2025
7
+
ms.date: 05/19/2025
8
8
audience: enabler
9
9
ms.topic: how-to
10
10
ms.service: microsoft-syntex
@@ -134,8 +134,12 @@ When the status of a request is **Completed**, **Canceled**, or **Declined**, th
134
134
> 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.
135
135
136
136
## Access the signed document
137
+
137
138
### 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.
139
143
140
144
> [!NOTE]
141
145
> 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
145
149
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.
146
150
147
151
### 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.
149
154
150
155
> [!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.
Copy file name to clipboardExpand all lines: microsoft-365/syntex/solutions/agreements-expirations.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ ms.author: chucked
4
4
author: chuckedmonson
5
5
manager: jtremper
6
6
ms.reviewer: vbarla
7
-
ms.date: 04/10/2025
7
+
ms.date: 05/19/2025
8
8
audience: admin
9
9
ms.topic: conceptual
10
10
ms.service: microsoft-syntex
@@ -44,11 +44,11 @@ If the **Expiration date** isn't included in the agreement, it's treated as an e
44
44
45
45
When the **Expiration date** field is filled in the agreement, the following actions occur:
46
46
47
-
**Two months before the expiration date:**
47
+
**Three months before the expiration date:**
48
48
49
49
- A reminder notification is sent to the [default recipients](#default-recipients-of-notifications), indicating the specific date the agreement will expire.
50
50
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.
0 commit comments