Different API response from different Azure Data Centers

%3CLINGO-SUB%20id%3D%22lingo-sub-1149240%22%20slang%3D%22en-US%22%3EDifferent%20API%20response%20from%20different%20Azure%20Data%20Centers%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1149240%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20are%20using%20MS%20Graph%20to%20execute%20a%20series%20of%20Teams%20related%20operations.%26nbsp%3B%20In%20particular%2C%20we%20are%20trying%20to%20get%20the%20Chat%20Thread%20Id%20to%20send%20proactive%20messages.%26nbsp%3B%20From%20Postman%2C%20we%20are%20able%20to%20execute%20the%20following%20without%20any%20issues%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3Ebeta%2Fusers%2F%7Buser%20id%7D%2Fchats%3F%24filter%3DinstalledApps%2Fany(a%3Aa%2FteamsApp%2Fid%2520eq%2520'%7Bteams%20app%20Id%7D')%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EThe%20response%20contained%20an%20x-ms-ags-diagnostic%20header%2C%20which%20carried%20the%20following%20information%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3E%7B%22ServerInfo%22%3A%7B%22DataCenter%22%3A%22South%20Central%20US%22%2C%22Slice%22%3A%22SliceC%22%2C%22Ring%22%3A%224%22%2C%22ScaleUnit%22%3A%22003%22%2C%22RoleInstance%22%3A%22AGSFE_IN_18%22%7D%7D%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EWhen%20we%20tried%20to%20repeat%20the%20call%20via%20a%20REST%20plugin%20in%20our%20automation%20platform%2C%20the%20call%20failed%20with%20a%20404.%26nbsp%3B%20The%20response%20also%20contained%20an%20x-ms-ags-diagnostic%20header%2C%20which%20carried%20the%20following%20information%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%7B%22ServerInfo%22%3A%7B%22DataCenter%22%3A%22West%20Europe%22%2C%22Slice%22%3A%22SliceC%22%2C%22Ring%22%3A%225%22%2C%22ScaleUnit%22%3A%22000%22%2C%22RoleInstance%22%3A%22AGSFE_IN_42%22%7D%7D%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt%20looks%20like%20the%20beta%2Fusers%2F%7Buser%20id%7D%2Fchats%20MS%20Graph%20API%20endpoint%20is%20not%20found%20in%20the%20West%20Europe%20data%20center%3F%26nbsp%3B%20Other%20calls%20in%20our%20automation%20platform%20(for%20eg.%26nbsp%3B%3CSPAN%3E%2Fv1.0%2Fusers%20or%20%2Fbeta%2Fusers%2F%7Buser%20id%7D%2Fteamwork%2FinstalledApps)%20are%20working%20fine%20though.%26nbsp%3B%20If%20this%20implies%20that%20there%20is%20an%20issue%20with%20the%20West%20Europe%20data%20center%2C%20is%20it%20possible%20to%20route%20traffic%20to%20a%20different%20data%20center%20programmatically%3F%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EPostman%20was%20executed%20locally%20on%20my%20machine%2C%20which%20is%20located%20in%20Asia%20while%20the%20automation%20platform%20is%20located%20outside%20of%20Asia.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EAny%20advice%3F%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EThank%20You%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1149240%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1934300%22%20slang%3D%22en-US%22%3ERe%3A%20Different%20API%20response%20from%20different%20Azure%20Data%20Centers%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1934300%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F493333%22%20target%3D%22_blank%22%3E%40voonsionglum%3C%2FA%3E%2C%20did%20you%20ever%20find%20anything%20with%20this%3F%20I%20am%20also%20seeing%20issues%20in%20Graph%20depending%20on%20what%20datacenter%20it%20is%20using.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fanswers%2Fquestions%2F175906%2Fgraph-api-returning-404-in-certain-data-centers-wh.html%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fanswers%2Fquestions%2F175906%2Fgraph-api-returning-404-in-certain-data-centers-wh.html%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fstackoverflow.com%2Fquestions%2F65013290%2Fgraph-api-returning-404-in-certain-data-centers-when-accessing-on-prem-mailbox%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fstackoverflow.com%2Fquestions%2F65013290%2Fgraph-api-returning-404-in-certain-data-centers-when-accessing-on-prem-mailbox%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1935267%22%20slang%3D%22en-US%22%3ERe%3A%20Different%20API%20response%20from%20different%20Azure%20Data%20Centers%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1935267%22%20slang%3D%22en-US%22%3EUnfortunately%2C%20no...%3C%2FLINGO-BODY%3E
Contributor

Hi,

 

We are using MS Graph to execute a series of Teams related operations.  In particular, we are trying to get the Chat Thread Id to send proactive messages.  From Postman, we are able to execute the following without any issues

 

beta/users/{user id}/chats?$filter=installedApps/any(a:a/teamsApp/id%20eq%20'{teams app Id}')

 

The response contained an x-ms-ags-diagnostic header, which carried the following information

 

{"ServerInfo":{"DataCenter":"South Central US","Slice":"SliceC","Ring":"4","ScaleUnit":"003","RoleInstance":"AGSFE_IN_18"}}

 

When we tried to repeat the call via a REST plugin in our automation platform, the call failed with a 404.  The response also contained an x-ms-ags-diagnostic header, which carried the following information

 

{"ServerInfo":{"DataCenter":"West Europe","Slice":"SliceC","Ring":"5","ScaleUnit":"000","RoleInstance":"AGSFE_IN_42"}}

 

It looks like the beta/users/{user id}/chats MS Graph API endpoint is not found in the West Europe data center?  Other calls in our automation platform (for eg. /v1.0/users or /beta/users/{user id}/teamwork/installedApps) are working fine though.  If this implies that there is an issue with the West Europe data center, is it possible to route traffic to a different data center programmatically?

 

Postman was executed locally on my machine, which is located in Asia while the automation platform is located outside of Asia.

 

Any advice?

 

Thank You

 

2 Replies
Unfortunately, no...