The “Service Not Available” error in Power Automate occurs when a connected service is temporarily down or unreachable. This issue can be caused by:
- Planned maintenance or unexpected outages of the service
- Network connectivity problems affecting Power Automate’s ability to reach the service
- Authentication or authorization issues preventing access
- API rate limits or throttling imposed by the external service
Error Message:
"Service not available – The connected service is temporarily unavailable."
2. Common Causes and Fixes
| Cause | Description | Fix |
|---|---|---|
| Service Outage | The external service is down for maintenance or experiencing an outage. | Check service status and wait for it to be restored. |
| Network Connectivity Issues | Power Automate cannot reach the service due to internet issues. | Ensure a stable internet connection and check firewall settings. |
| Authentication Errors | Expired or invalid credentials prevent access. | Re-authenticate and reconnect the service. |
| API Rate Limits Exceeded | Too many requests were sent in a short time, triggering throttling. | Reduce request frequency and implement retry policies. |
| Incorrect Connector Configuration | The connector settings are misconfigured or outdated. | Verify API endpoint, credentials, and permissions. |
3. Step-by-Step Troubleshooting Guide
Step 1: Check Service Status for Outages
If the issue is due to a service outage, you need to wait for it to be resolved.
How to check service status:
- Microsoft Services: https://status.office365.com
- Power Platform Services: https://learn.microsoft.com/en-us/power-platform/admin/service-health-dashboard
- Third-Party APIs: Check the service provider’s status page (e.g., Salesforce, Google, or custom APIs).
Example Fix:
- If SharePoint Online is down, wait until Microsoft restores service.
Step 2: Reconnect the Service in Power Automate
Sometimes, service disruptions require you to re-establish the connection.
Steps to reconnect:
- Open Power Automate.
- Navigate to Data → Connections.
- Find the affected connection and click Fix Connection.
- Re-enter authentication credentials if prompted.
Example Fix:
- If a SQL Server connector fails, disconnect and reconnect with valid credentials.
Step 3: Verify Network and Firewall Settings
If the service is blocked by a firewall or proxy, Power Automate may not be able to connect.
Steps to check network settings:
- Try accessing the service manually in a web browser.
- Ensure that Power Automate’s IP ranges are whitelisted (for on-premise services).
- If using a VPN or proxy, try disabling it and test again.
Example Fix:
- If accessing an on-premises SQL Server, ensure the on-premises data gateway is running.
Step 4: Reduce API Request Frequency to Prevent Throttling
If the service blocks requests due to excessive API calls, you may need to implement rate limiting strategies.
Steps to fix:
- Open Power Automate and locate the flow.
- Add a delay action (5-10 seconds) before calling the service again.
- Enable Retry Policy under action settings and set it to Exponential Backoff.
Example Fix:
- If calling Microsoft Graph API, limit requests to 10,000 per 10 minutes per user.
Step 5: Check Authentication Credentials and Permissions
If authentication fails, the service may reject requests.
Steps to fix:
- Ensure the credentials used in Power Automate are correct and active.
- If using OAuth tokens, check if they have expired and re-authenticate.
- Verify that the connected account has sufficient permissions.
Example Fix:
- If a Google Drive connector fails, re-authorize with Google permissions.
Step 6: Use Alternative Endpoints or Backup Services
If the primary service is down, try using a secondary API endpoint or a different service.
Steps to fix:
- Check if the service has a secondary data center or alternate API URL.
- If possible, switch to another service temporarily.
Example Fix:
- If an Azure Storage Account API is unavailable, switch to a redundant region.