Workaround Advice for PowerApps <=> Azure issues?

(1) Share

Report

Posted on by BL-30071457-0

Hi everyone,

Hoping to get some advice for some temporary workarounds here. PowerApps essentially cannot connect to Azure SQL databases via cloud services right now - been an issue for 14 days, and posted as a live outage in the admin portal under issue 6576827 for 7 days.

We have a particular PowerApp we use for time entry, invoicing, and more, and it's all at a near complete standstill. We have no direct line to the teams working on this, and the contracted support teams, when they reach out to engineering, just come back that it's in progress and there's no ETA.

Third time this has happened in three months as well, but at two weeks this is the longest one so far - so any tips or advice here would be much appreciated!

Thank you!

Categories:

Error handling

I have the same question (0)

All responses (2)

Answers (0)

Sort by

Suggested answer

11manish 3,768 on at

Like
a
(0)

Report
Copy link

Link copied!

If Microsoft has already acknowledged this as an active service incident and your symptoms match the advisory, there's unfortunately no application-level fix until the service is restored.

Given that this is the third occurrence in three months and the current outage has lasted over two weeks, I'd avoid making significant architectural changes solely to work around this incident. Instead, implement a temporary fallback (such as SharePoint or Dataverse for data capture) to maintain business operations while Microsoft resolves the issue. After the incident is closed, it would be worth reviewing your architecture to determine whether critical workloads should rely exclusively on the native Azure SQL connector or whether an API layer would provide greater resilience during future service disruptions.

Was this reply helpful? Yes No
Suggested answer

Haque 3,955 on at

Like
a
(1)

Report
Copy link

Link copied!

Hi @BL-30071457-0,

Without waiting what we can do is open or escalate support tickets referencing the known outage (e.g., issue 6576827), it will accelarate the significances/importances. Also, request updates and ask for any possible mitigation steps with ETA.

If things are really business critical can we consider temporary workarounds (like 11manish suggested)? I mean switching to a different data source. Also, Use cached or offline data entry modes if your app supports it so that we can sync up later when system is resoted.

There is no gurantee that this will come again ( thrice in three months mean - a dozen times in 1 year - datum talk!). Clearly we need a future resilience. From now on we need to evaluate disaster recovery and failover polices for the apps you are going to build. If it allows (costly may be), can we consider multi-region or multi database redundancy?

Was this reply helpful? Yes No