This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(6.4, 90%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMR%3C/text%3E%3C/svg%3E)
Please can you confirm why the communications/callRecords endpoint is down, I have not been able to connect to it since 09:19 GMT.
{
"error": {
"code": "General",
"message": "Internal service 'Microsoft.Graph.Services.CallRecords' is unavailable.",
"innerError": {
"request-id": "d7cbf996-9835-4d60-addd-88d68d3c96a2",
"date": "2024-03-01T15:09:19",
"client-request-id": "d7cbf996-9835-4d60-addd-88d68d3c96a2"
}
}
}
An API that connects multiple Microsoft services, enabling data access and automation across platforms
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(28.799999999999997, 88%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJJ%3C/text%3E%3C/svg%3E)
Yeah having the same issue, its been up-and-down since Friday last week
This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(307.2, 93%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMD%3C/text%3E%3C/svg%3E)
Our ticket got resolved and Microsoft released a Service Health Advisory last Friday.
The service was indeed back to normal.
But currently we are experiencing the same issue.
Anyone else who can confirm the same?
Yes looks like it went again at 9:27 this morning.
Dimitri, can I get the MS "Service Health Advisory" link please? As I cant find one for Friday?
This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Root cause: A portion of infrastructure responsible for the functionality of the call records API, which Microsoft Teams relies on to provide call record data, wasn't performing as expected.
Seems Microsoft does not allow to share the Service Health Advisory ID / link here.
They block my message
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(233.6, 7.000000000000001%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMA%3C/text%3E%3C/svg%3E)
yes for me too, actually it's very annoying!
"message": "Internal service 'Microsoft.Graph.Services.CallRecords' is unavailable."
Is the Service Health Advisory in Azure? Or Somewhere else?
SO looks like if you keep trying and set the timeout to 100 seconds eventually I get a response but getting many errors before I do eventually get through.
The Service Health Advisory is visible in the MS365 Admin Center... but maybe only in our tenant.
We are still experiencing the issue and raised the severity of our case with MS
Since yesterday we are not experiencing the problem anymore
As of 18:19 GMT the service looks to be back online. so was down for over 9 hours.
There is nothing official from Microsoft I can find??
We have raised a ticket with Microsoft
We have opened a ticket and its under "investigating"
For us too!!!
We are experiencing the same problem since this morning.