Microsoft Teams Development
Microsoft Teams: A Microsoft customizable chat-based workspace.Development: The process of researching, productizing, and refining new or existing technologies.
3,035 questions
Msteams bot custom tab sso failing with error code 2605 ServerTemporarilyUnavailable
![](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(86.4, 31%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESJ%3C/text%3E%3C/svg%3E)
Saurabh Jagtap
5
Reputation points
Hi, we have msteams bot with custom tab in it. We use msal.js for automated sso as per this doc. Since today morning, we are suddenly getting the error:
{"Description":"(pii)","Domain":"com.microsoft.oneauth","ErrorCode":"2605","Message":"The server is temporarily unavailable","SystemErrorCode":"3399614469","Tag":"7q6ci","Type":"OneAuth","additional_query_parameters_count":"1","all_error_tags":"7q6ci|7q6ci","api_error_code":"3399614469","api_error_context":"(pii)","api_error_tag":"7q6ci","api_name":"AcquireTokenSilently","api_status_code":"StatusInternal::ServerTemporarilyUnavailable","auth_flow":"Broker","authority_type":"AAD","authorization_type":"WindowsIntegratedAuth","broker_app_used":"true","broker_error_location":"7q6ci","client_id":"1fec8e78-bce4-4aaf-ab1b-5451cc387264","correlation_id":"39b75d91-dcc0-48c4-82f2-7e8f880a2299","is_successful":"false","msal_version":"1.1.0+00747db6","original_authority":"https://login.microsoftonline.com/513294a0-3e20-41b2-a970-6d30bf1546fa","read_token":"ID","request_duration":"484","request_eligible_for_broker":"true","start_time":"2024-06-24T08:34:35.000Z","stop_time":"2024-06-24T08:34:35.000Z","wam_telemetry":"{\"ui_visible\":false,\"scope\":\"api://chatteron.io/7313ffbd-0d2f-4ee7-85d8-ae2cff842ebc/.default offline_access openid profile\",\"redirect_uri\":\"ms-appx-web://Microsoft.AAD.BrokerPlugin/1fec8e78-bce4-4aaf-ab1b-5451cc387264\",\"provider_id\":\"https://login.windows.net\",\"oauth_error_code\":\"authentication_failed\",\"device_join\":\"dj\",\"correlation_id\":\"{39b75d91-dcc0-48c4-82f2-7e8f880a2299}\",\"client_id\":\"1fec8e78-bce4-4aaf-ab1b-5451cc387264\",\"cache_event_count\":0,\"broker_version\":\"10.0.22621.3672\",\"authority\":\"https://login.microsoftonline.com/513294a0-3e20-41b2-a970-6d30bf1546fa\",\"api_error_code\":-894893983,\"account_join_on_start\":\"primary\",\"account_join_on_end\":\"primary\",\"silent_code\":0,\"silent_bi_sub_code\":0,\"silent_message\":\"\",\"silent_status\":0,\"is_cached\":0}","was_request_throttled":"false"}
Can someone help with the issue? looks like an issue from microsoft backend.
We have tried to logout and relogging in the user, if there is any token cache issue. Also reinstalling the manifest to the user.
Microsoft Teams Development
{count} vote
-
![](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(214.4, 10%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDR%3C/text%3E%3C/svg%3E)
Dinesh Rajagoni (Tata Consultancy Services Limi) 50 Reputation points Microsoft Vendor2024-06-24T19:34:06.63+00:00 Hi Saurabh Jagtap - Thanks for raising the query. The error code 2605 indicates a temporary server issue, often linked to MSAL.js SSO authentication in Teams bots. To resolve this, please:
Verify MSAL.js settings to ensure silent token acquisition is configured correctly.
Check Azure Portal for proper setup in client applications and authorized clients.
If problems persist, please feel free to reply on this thread.
-
Saurabh Jagtap 5 Reputation points
2024-07-02T10:10:57.5333333+00:00 Thanks for replying @Dinesh Rajagoni (Tata Consultancy Services Limi) !
We have verified both the msal.js and azure portal configurations and they are correct. We have been using this since couple of years. After I posted the question in the forum, the issue stopped coming up automatically by itself, but suddenly again the same issue is coming up. I have confirmed again that we are using the same configurations and nothing has been changed from our end.
If this is a temporary server issue, is there any server status page or something where we can check the server status? On any incident reports, downtime reports, or changes that are being done in backend? Or specific reasons that we can communicate to our users that why is this happening?
Sign in to comment