Provide the Post-Incident Review (PIR) document of a specified service issue for tenant.
An issue only with status of PostIncidentReviewPublished indicates that the PIR document exists for the issue. The operation returns an error if the specified issue doesn't exist for the tenant or if PIR document does not exist for the issue.
Choose the permission or permissions marked as least privileged for this API. Use a higher privileged permission or permissions only if your app requires it. For details about delegated and application permissions, see Permission types. To learn more about these permissions, see the permissions reference.
Permission type
Least privileged permissions
Higher privileged permissions
Delegated (work or school account)
ServiceHealth.Read.All
Not available.
Delegated (personal Microsoft account)
Not supported.
Not supported.
Application
ServiceHealth.Read.All
Not available.
HTTP request
GET /admin/serviceAnnouncement/issues/{serviceHealthIssueId}/incidentReport
GET https://graph.microsoft.com/v1.0/admin/serviceAnnouncement/issues/MO248163/incidentReport
// Code snippets are only available for the latest version. Current version is 5.x
// To initialize your graphClient, see https://learn.microsoft.com/en-us/graph/sdks/create-client?from=snippets&tabs=csharp
await graphClient.Admin.ServiceAnnouncement.Issues["{serviceHealthIssue-id}"].IncidentReport.GetAsync();
// THE CLI IS IN PREVIEW. NON-PRODUCTION USE ONLY
mgc admin service-announcement issues incident-report get --service-health-issue-id {serviceHealthIssue-id}
// Code snippets are only available for the latest version. Current version is 6.x
GraphServiceClient graphClient = new GraphServiceClient(requestAdapter);
graphClient.admin().serviceAnnouncement().issues().byServiceHealthIssueId("{serviceHealthIssue-id}").incidentReport().get();
<?php
use Microsoft\Graph\GraphServiceClient;
$graphServiceClient = new GraphServiceClient($tokenRequestContext, $scopes);
$graphServiceClient->admin()->serviceAnnouncement()->issues()->byServiceHealthIssueId('serviceHealthIssue-id')->incidentReport()->get()->wait();
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see: https://aka.ms/ContentUserFeedback.