MS Graph HTTP request failed with status code: GatewayTimeout

Question

MS Graph HTTP request failed with status code: GatewayTimeout

Dimitry Decan 0

Hi everyone,

Lately my runbook has been spewing out following error User's image

The runbook has been running perfectly fine for the past months, but since last week this started to appear.

Anyone else having similar behaviour?

Dimitry Decan 0 Reputation points

2025-07-14T14:54:26.1466667+00:00

Hi Vinod,

Thank you for your quick reply.

As mentioned before. The runbook was running properly for the last months.
Starting from last week we have 1 day that it runs and the next day it does not run.

It also depends on the tenant.
The runbook goes over multiple clients and 1 client has the issue and another does not have the issue. But then the next day its working, and then the next its not.
Rahul Jorrigala 4,410 Reputation points Microsoft External Staff Moderator

2025-07-14T16:36:26.3133333+00:00

Hello @Dimitry Decan,

Addition to Vinod's statement.

As per error, the backend service might be experiencing high load or temporary downtime. If the request takes too long to process, it may time out.

Based on your description, it sounds like you're dealing with intermittent failures in an Azure Automation runbook that targets multiple tenants.

Check the Activity Logs to see if any modules were updated around the time the issue began. If not, review the modules used in the runbook and check if newer versions are available for update.

To isolate the issue, try sending the same request using Postman or curl and see if it consistently fails.

Please let me know if you face any challenge here, I can help you to resolve this issue further

If the comment was helpful, please click "Upvote"
Eric Ericbejlic 0 Reputation points

2025-07-14T17:46:29.05+00:00

Recent change or update triggered the issue. Check for updates to dependencies or platform changes. You’re not alone others have reported similar runbook errors lately.
Rahul Jorrigala 4,410 Reputation points Microsoft External Staff Moderator

2025-07-15T04:52:43.7066667+00:00

Hello @Dimitry Decan,

Just want to check if the above Comment worked for you or else please let us know if any help, we are always here to help whenever you need us.

If the comment is helpful, please click "Upvote it"

Thankyou
Dimitry Decan 0 Reputation points

2025-07-15T14:06:51.7633333+00:00

These answers are for sure useful, but didn't really help.

Is there any official Microsoft communication that states there are high load issues for MS Graph?

We also noticed that tenants which are located in Amsterdam experience no issues.
Tenants who are not in Amsterdam experience issues.
Naveena Patlolla 8,520 Reputation points Microsoft External Staff Moderator

2025-07-15T18:42:01.8766667+00:00

Hi Dimitry Decan

1.Please check the service health using below link.

https://portal.azure.com/#blade/Microsoft_Azure_Health/AzureHealthBrowseBlade

2.Test Graph API Manually: Run the same API call using Postman or PowerShell outside Automation to confirm if it’s a general issue or issue with automation account.

Please "Upvote" if it was helpful.
Vinod Pittala 6,410 Reputation points Microsoft External Staff Moderator

2025-07-16T15:03:16.7766667+00:00

Hi Dimitry Decan,

have you had a chance to review the Naveena Patlolla's comment ?

Thanks
Naveena Patlolla 8,520 Reputation points Microsoft External Staff Moderator

2025-07-16T22:37:06.17+00:00

Hello Dimitry Decan,

Just want to check if the above Comment worked for you or else please let us know if any help, we are always here to help whenever you need us.

If the comment is helpful, please click "Upvote it"

Thankyou
Dimitry Decan 0 Reputation points

2025-07-17T06:58:27.0966667+00:00

Hi,

If I remember correctly it also didn't work outside of the Automation account.
I will try to find time to retest this today.

Is there any documentation on Tenant location?

e.g. when we go to a customers we see the following:

Tenant location: Europe 0202 or OData points to AMSUB0202 (this clearly shows Amsterdam)
We have another customers with Tenant location: Europe 0601 which points to MSUB06
What Datacenter location is MSUB06? Because we seem to have the issues when its NOT Amsterdam.

Thanks in advance.
Dimitry Decan 0 Reputation points

2025-07-17T13:20:20.21+00:00

To follow up on this.

I just tested the runbook for quite some time and I got 0 timeouts.
Same thing locally I've had 0 timeouts.

Seems like its temporarily solved. Ofcourse this was already the case these last weeks. 1 day it works and the other we get timeouts (Runbook & Local).
Vinod Pittala 6,410 Reputation points Microsoft External Staff Moderator

2025-07-17T14:53:06.1366667+00:00

Hello Dimitry Decan,

Thanks for the confirmation on the recent testing. as i believed from starting, there could be definitely a intermittent network issues from the particular customer. because as you confirmed its failing sometime and succeeding other time, which indicates intermittent network issues are there.

so, resolve the issue permanently, i request you have the private connection all the times. so that this will help eliminate intermittent disruptions and provide a more stable communication channel.

Please let me know if you need assistance, I'm happy to help.

Thanks
Naveena Patlolla 8,520 Reputation points Microsoft External Staff Moderator

2025-07-17T21:24:56.3566667+00:00

Hello Dimitry Decan,

Just want to check if the above Comment provided by @Vinod Pittala worked for you or else please let us know if any help, we are always here to help whenever you need us.

If the comment is helpful, please click "Upvote it"

Thankyou
Dimitry Decan 0 Reputation points

2025-07-18T05:05:31.8366667+00:00

Our customer has no network issues. We tested this. We are almost certain that the issue is on Microsoft side. Overload of MSGraph request i would assume. It happens to customers that have their tenants NOT in Amsterdam. As I asked before for documentation on this this question remains to be answered. Nonetheless I thank you for your efforts and quick response.

1 answer

Your answer

Dimitry Decan 0 Reputation points

2025-07-14T14:54:26.1466667+00:00

Hi Vinod,

Thank you for your quick reply.

As mentioned before. The runbook was running properly for the last months.
Starting from last week we have 1 day that it runs and the next day it does not run.

It also depends on the tenant.
The runbook goes over multiple clients and 1 client has the issue and another does not have the issue. But then the next day its working, and then the next its not.
Rahul Jorrigala 4,410 Reputation points Microsoft External Staff Moderator

2025-07-14T16:36:26.3133333+00:00

Hello @Dimitry Decan,

Addition to Vinod's statement.

As per error, the backend service might be experiencing high load or temporary downtime. If the request takes too long to process, it may time out.

Based on your description, it sounds like you're dealing with intermittent failures in an Azure Automation runbook that targets multiple tenants.

Check the Activity Logs to see if any modules were updated around the time the issue began. If not, review the modules used in the runbook and check if newer versions are available for update.

To isolate the issue, try sending the same request using Postman or curl and see if it consistently fails.

Please let me know if you face any challenge here, I can help you to resolve this issue further

If the comment was helpful, please click "Upvote"
Eric Ericbejlic 0 Reputation points

2025-07-14T17:46:29.05+00:00

Recent change or update triggered the issue. Check for updates to dependencies or platform changes. You’re not alone others have reported similar runbook errors lately.
Rahul Jorrigala 4,410 Reputation points Microsoft External Staff Moderator

2025-07-15T04:52:43.7066667+00:00

Hello @Dimitry Decan,

Just want to check if the above Comment worked for you or else please let us know if any help, we are always here to help whenever you need us.

If the comment is helpful, please click "Upvote it"

Thankyou
Dimitry Decan 0 Reputation points

2025-07-15T14:06:51.7633333+00:00

These answers are for sure useful, but didn't really help.

Is there any official Microsoft communication that states there are high load issues for MS Graph?

We also noticed that tenants which are located in Amsterdam experience no issues.
Tenants who are not in Amsterdam experience issues.
Naveena Patlolla 8,520 Reputation points Microsoft External Staff Moderator

2025-07-15T18:42:01.8766667+00:00

Hi Dimitry Decan

1.Please check the service health using below link.

https://portal.azure.com/#blade/Microsoft_Azure_Health/AzureHealthBrowseBlade

2.Test Graph API Manually: Run the same API call using Postman or PowerShell outside Automation to confirm if it’s a general issue or issue with automation account.

Please "Upvote" if it was helpful.
Vinod Pittala 6,410 Reputation points Microsoft External Staff Moderator

2025-07-16T15:03:16.7766667+00:00

Hi Dimitry Decan,

have you had a chance to review the Naveena Patlolla's comment ?

Thanks
Naveena Patlolla 8,520 Reputation points Microsoft External Staff Moderator

2025-07-16T22:37:06.17+00:00

Hello Dimitry Decan,

Just want to check if the above Comment worked for you or else please let us know if any help, we are always here to help whenever you need us.

If the comment is helpful, please click "Upvote it"

Thankyou
Dimitry Decan 0 Reputation points

2025-07-17T06:58:27.0966667+00:00

Hi,

If I remember correctly it also didn't work outside of the Automation account.
I will try to find time to retest this today.

Is there any documentation on Tenant location?

e.g. when we go to a customers we see the following:

Tenant location: Europe 0202 or OData points to AMSUB0202 (this clearly shows Amsterdam)
We have another customers with Tenant location: Europe 0601 which points to MSUB06
What Datacenter location is MSUB06? Because we seem to have the issues when its NOT Amsterdam.

Thanks in advance.
Dimitry Decan 0 Reputation points

2025-07-17T13:20:20.21+00:00

To follow up on this.

I just tested the runbook for quite some time and I got 0 timeouts.
Same thing locally I've had 0 timeouts.

Seems like its temporarily solved. Ofcourse this was already the case these last weeks. 1 day it works and the other we get timeouts (Runbook & Local).
Vinod Pittala 6,410 Reputation points Microsoft External Staff Moderator

2025-07-17T14:53:06.1366667+00:00

Hello Dimitry Decan,

Thanks for the confirmation on the recent testing. as i believed from starting, there could be definitely a intermittent network issues from the particular customer. because as you confirmed its failing sometime and succeeding other time, which indicates intermittent network issues are there.

so, resolve the issue permanently, i request you have the private connection all the times. so that this will help eliminate intermittent disruptions and provide a more stable communication channel.

Please let me know if you need assistance, I'm happy to help.

Thanks
Naveena Patlolla 8,520 Reputation points Microsoft External Staff Moderator

2025-07-17T21:24:56.3566667+00:00

Hello Dimitry Decan,

Just want to check if the above Comment provided by @Vinod Pittala worked for you or else please let us know if any help, we are always here to help whenever you need us.

If the comment is helpful, please click "Upvote it"

Thankyou
Dimitry Decan 0 Reputation points

2025-07-18T05:05:31.8366667+00:00

Our customer has no network issues. We tested this. We are almost certain that the issue is on Microsoft side. Overload of MSGraph request i would assume. It happens to customers that have their tenants NOT in Amsterdam. As I asked before for documentation on this this question remains to be answered. Nonetheless I thank you for your efforts and quick response.

Answer 1

Hello Dimitry Decan,

If your runbook is encountering a Gateway Timeout error when trying to make an HTTP request to the Microsoft Graph API. This issue can often be related to network connectivity problems or misconfigured settings.

Here are a few steps you can take to troubleshoot this error:

Check Network Connectivity:
- Ensure that the domain ex: gcs.office.com (or the appropriate one for your tenant) is reachable. You can do this by running the following command in PowerShell
```
     
     tnc gcs.office.com -Port 443
     
```
  You should see TcpTestSucceeded: True. If not, check your firewall or proxy settings.
Test the Endpoint:
- Run this command to check if the endpoint is responding properly:
```
     wget https://gcs.office.com/v1.0/admin/AdminDataSetCrawl/healthcheck
```
  A successful response will return StatusCode: 200. If not, you might need to look into proxy/firewall configurations again.
Review Logs:
- If the above tests pass, check the GCA logs for any potential network issues. Look in these locations:
- For Windows Server 2016:
```
      C:\Users\GcaHostService\AppData\Local\Microsoft\GraphConnectorAgent\HostService\logs
```
- For other supported Windows OS:
```
      C:\Windows\ServiceProfiles\GcaHostService\AppData\Local\Microsoft\GraphConnectorAgent\HostService\logs
```
- Open the two most recent log files and check for error messages related to network connectivity.
Check Proxy Settings:
- If there are network proxy issues indicated in your logs, confirm that the virtual account (NT Service\GcaHostService) has permission to send traffic to the necessary domains.

If the command helpful, please click upvote it.

Thanks

Ahsan Sahab 0 Reputation points

2026-02-23T10:57:52.89+00:00

“MS Graph HTTP request failed with status code: GatewayTimeout” means your request to Microsoft Graph API did not get a response in time from the server. A Gateway Timeout (504 error) usually happens when the server is overloaded, the request takes too long to process, or there is a network issue between services.

To fix it, you can try reducing the size of your request (for example, limit query results), check your internet connection, increase timeout settings in your application, or retry the request after some time.

Share via

MS Graph HTTP request failed with status code: GatewayTimeout

1 answer

Your answer