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: microsoft-365/enterprise/microsoft-365-admin-engagements.md
+91-3Lines changed: 91 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,15 +5,15 @@ f1.keywords:
5
5
ms.author: vpattnaik
6
6
author: vpattnai
7
7
manager: dansimp
8
-
ms.date: 01/27/2026
8
+
ms.date: 04/27/2026
9
9
audience: Admin
10
10
ms.reviewer: dansimp
11
11
ms.topic: article
12
12
ms.service: microsoft-365-enterprise
13
13
ms.localizationpriority: medium
14
14
ms.collection:
15
15
- m365admin
16
-
description: The Engagements pivot in Enhanced engagements offers a centralized overview of all customer-specific engagements with Microsoft.
16
+
description: The Engagements section in Enhanced engagements offers a centralized overview of all customer-specific engagements with Microsoft.
17
17
ai-usage: ai-assisted
18
18
---
19
19
@@ -180,8 +180,8 @@ If a CAB event or call hasn’t been scheduled yet, the corresponding date and d
180
180
### Upcoming CAB schedule
181
181
182
182
The **Upcoming CAB schedule** lists all planned engagements with Microsoft 365 engineering teams. Each entry provides event details, topics, audience, and registration information.
183
-
You can:
184
183
184
+
You can:
185
185
-**View** upcoming and past CAB sessions.
186
186
-**Export** the schedule for tracking and internal coordination.
187
187
-**Register** for upcoming sessions directly from the portal.
@@ -209,6 +209,94 @@ The Customer Advisory Board program allows you to:
209
209
- Network with peers across industries facing similar challenges.
210
210
- Influence future product and service enhancements.
211
211
212
+
## Incident Analysis
213
+
214
+
The Incident Analysis page in Enhanced engagements allows you to request incident analysis for closed incidents. You can submit a request for incidents that have been critical in nature and resolved in the last 7 days. In addition, you can view insights into your current incident analysis requests, including their status, and see a report of all past requests.
215
+
216
+
:::image type="content" source="../media/enhanced-engagements/incident-analysis-engagements.png" alt-text="Screenshot that shows a dashboard with sections for engaging in incident analysis, requesting analysis for closed critical incidents, and submitting a new incident request." lightbox="../media/enhanced-engagements/incident-analysis-engagements.png":::
217
+
218
+
### Create an Incident Analysis request
219
+
220
+
To submit an incident analysis request:
221
+
222
+
1. Go to the **Incident Analysis** page and navigate to the Incident Analysis section under **Engagements**.
223
+
224
+
2. Select **Create a new request**. A flyout menu will open, showing a list of eligible incidents that can be selected for incident analysis.
225
+
226
+
3. Select a case. In the flyout menu, choose an incident by selecting the ticket number from the available list.
227
+
228
+
4. Review case details after selecting an incident where you'll also see additional details related to the ticket. Follow the prompts to complete your analysis request.
229
+
230
+
5. If it's a Copilot issue, check the box.
231
+
232
+
6. Submit your request. Once you've reviewed the information, submit your incident analysis request.
233
+
234
+
:::image type="content" source="../media/enhanced-engagements/submit-incident-analysis.png" alt-text="Screenshot that shows a selection interface for submitting an incident analysis, with a list of technical issue categories such as Exchange, SharePoint, and Copilot for Microsoft 365." lightbox="../media/enhanced-engagements/submit-incident-analysis.png":::
235
+
236
+
Alternatively, you can do the following:
237
+
238
+
1. If you do not see your incident listed, select **Don’t see your incident**.
239
+
240
+
2. A flyout menu will open. Provide your case number and contact details, explain why this case should qualify for Incident Analysis, and outline the specific information you seek if eligible.
241
+
242
+
3. Submit your request. All requests will be reviewed by a Technical Customer Lead (TCL).
243
+
244
+
:::image type="content" source="../media/enhanced-engagements/manually-submit-request-incident-analysis.png" alt-text="Screenshot that shows a form for submitting an Incident Analysis request, including fields for case number, contact information, description, and a submit button." lightbox="../media/enhanced-engagements/manually-submit-request-incident-analysis.png":::
245
+
246
+
### Incident Analysis Overview
247
+
248
+
The Incident Analysis (IA) overview section provides a snapshot of the current state of your incident analysis requests:
249
+
250
+
-**Total IAs**: Displays the total number of open incident analysis requests.
251
+
252
+
-**Active IAs**: Shows the number of active requests that are being worked on.
253
+
254
+
### Active IAs by workload
255
+
256
+
This section breaks down your active incident analysis requests by workload type:
257
+
258
+
-**Exchange**: The number of active analysis requests related to Exchange incidents.
259
+
260
+
-**SharePoint**: The number of active analysis requests related to SharePoint incidents.
261
+
262
+
-**Teams**: The number of active analysis requests related to Teams incidents.
263
+
264
+
-**Copilot for M365**: The number of active analysis requests related to Copilot incidents
265
+
266
+
### Incident analysis filters
267
+
268
+
You can refine your view of the incident analysis requests by using the following filters:
269
+
270
+
-**Status**: Filter by the status of the request (for example, _Submitted_, _Completed_).
271
+
272
+
-**Created By**: Filter by the user who created the request.
273
+
274
+
-**Product**: Filter by the product associated with the incident (for example, _Exchange_, _SharePoint_, _Teams_, _Copilot for M365_).
275
+
276
+
### Request Report
277
+
278
+
The **Request Report** section displays a table with all the incident analysis requests that have been submitted. For each request, you can see the following details:
279
+
280
+
-**Ticket #**: The unique identifier for the incident.
281
+
282
+
-**Case Title**: The title of the incident request.
283
+
284
+
-**Status**: The current status of the request (for example, *Submitted*, *Completed*).
285
+
286
+
-**Created By**: The user who created the request.
287
+
288
+
-**Date Created**: The date when the request was created.
289
+
290
+
-**Product**: The product associated with the incident (for example, *Exchange*, *SharePoint*, *Teams, Copilot for M365*).
291
+
292
+
## Navigation and Pagination
293
+
294
+
The request report is displayed in a paginated table format. You can navigate through the pages of requests by using the pagination controls at the bottom of the table:
295
+
296
+
-**Next** and **Previous** arrows allow you to move between pages.
297
+
298
+
- The **Items per page** selector lets you adjust how many requests are displayed on each page.
299
+
212
300
## Related content
213
301
214
302
-[Diagnostics pivot in Enhanced Engagements portal](microsoft-365-admin-diagnostics.md)
0 commit comments