Issue Summary

Azure will sometimes report a 500 internal server error for provisioning into Atlassian.

Steps to Reproduce

1. Setup provisioning between Azure AD and Atlassian Access
2. Azure will regularly call the Atlassian SCIM APIs to check if the synced data is up to date or to update data.

Actual Results

Azure will sometime receive a 500 internal server error response from the API calls and will warn the users.

While attempting to validate our authorization to access your System for Cross Domain Identity Management service, we received this unexpected response:
Received response from Web resource.

Resource: https://api.atlassian.com/scim/directory/<DIRECTORYID>/scim/XXXX
Operation: GET
Response Status Code: InternalServerError
Response Content: 
{"timestamp":"20XX-XX-XXT11:52:31.911+0000",
"status":500,
"error":"Internal Server Error",
"exception":"com.netflix.zuul.exception.ZuulException",
"message":"GENERAL"}

Or in some cases, Azure will receive the same 500 response but a different exception:

Resource: https://api.atlassian.com/scim/directory/<DIRECTORYID>/scim/XXXX
Operation: GET
Response Status Code: InternalServerError
Response Content: 
{"timestamp":"20XX-XX-XXT11:52:31.911+0000",
"status":500,
"error":"Internal Server Error",
"exception":"io.atlassian.stargate.GatewayException",
"message":"GENERAL"}

Expected Results

There should be better handling for the message by Azure or messaging for the 500 response code should be improved.

Workaround

When Azure encounters an error, there will be a retry mechanism that will kick in. Usually the message can be ignored. If the Atlassian Cloud app in Azure has been quarantined due to too much errors, contact support.