Known Issue: Azure outage issue causing unexpected client errors in LCS and Finance and Operations


[Update - 13th September, 2018 - All issues related to this outage have been resolved. ]

[Update: Most of the services that were impacted as a result of this outage have now been recovered. So many of the issues that you were experiencing yesterday should now be fixed. The only known issue at this point is the environment monitoring page in LCS throwing errors. The backing service for this page is not completely recovered and we are working with the Azure team to get this resolved. We will update this blog post once this issue is resolved.]

 

Due to an Azure outage in some regions impacting services like Visual Studio Team Services, Azure Active Directory, etc. some customers might get an "Unexpected client error" when logging into the Finance and Operations or Lifecycle Services product, accessing your code in VSTS, trying to sync BPM libraries, trying to submit a support incident from the product, or when trying to submit a service request (for environment deployment, updating production or moving databases across environments) to our service engineering team.

To submit a support incident to Microsoft, you have two options:

  1. If you are able to login to LCS, you can submit an issue to Microsoft through LCS "Submit to Microsoft" button.
  2. If you are unable to login to LCS, you can contact support directly via phone. For region specific support numbers, please check the Contact support site.

There is currently no workaround for submitting a service request, as a result, this will be enabled once the issue has been resolved

We are working with the Azure team to get this issue resolved quickly. We will update this blog post once this issue is resolved.


Comments (0)

Skip to main content