Resolved -
The OrbusInfinity connector for Power Automate is now fully operational and authenticating as normal. Following Microsoft publishing the updated connector, we have monitored connections over the past few days and confirmed service is stable, so we are marking this incident as resolved.
No action is required on your part. If you continue to experience any connection or authorisation errors, please try reconnecting the connector, and contact Orbus Support if the problem persists.
Thank you for your patience and understanding throughout this incident.
Aug 10, 09:40 UTC
Monitoring -
Microsoft has published the updated OrbusInfinity connector for Power Automate. The issue is now resolved, we are continuing to monitor any potential problems.
Aug 6, 10:53 UTC
Update -
We are still awaiting Microsoft to publish the updated OrbusInfinity connector for Power Automate. There is no change to report at this stage, and we do not yet have an ETA, but we are continuing to chase this with Microsoft as a priority. We will update here as soon as we have more to share. Thank you for your continued patience.
Jul 31, 15:14 UTC
Update -
We are continuing to work with Microsoft to restore the OrbusInfinity connector for Power Automate. The change required is still pending on Microsoft's side, and we are awaiting the updated connector to be published. We do not have an ETA at this time, but we will update here as soon as we have more to share. Thank you for your continued patience.
Jul 28, 13:04 UTC
Identified -
We are aware of an issue affecting the OrbusInfinity connector for Power Automate. Affected connections are currently unable to authenticate, and you may see an authorisation error (e.g. an "OAuth2 authorization flow failed" or "invalid client" message) when a flow attempts to connect to OrbusInfinity.
This is caused by an authentication credential on the Orbus side that requires renewal. The renewal was submitted ahead of the expiry, and the necessary change is now with Microsoft to apply. Service will be restored once Microsoft have completed the work on their side. We do not currently have an ETA for completion and this may take some time.
You do not need to change anything on your end. We are working with Microsoft and will post further updates here as we make progress, confirming once connections are fully restored. Thank you for your patience.
Jul 18, 12:00 UTC