Connection Issues
Having trouble connecting to a data source or workspace? Here are the most common issues and how to resolve them.
Connection Test Fails
When Test Connection fails in the Environment Editor:
- Check your credentials. Server name, database name, username, and password all need to be correct.
- Check network access. Can your machine reach the server? For cloud databases, make sure your IP address is allowed through the firewall.
- Try a longer timeout. Connections that require MFA can take a while. The default timeout is 120 seconds, which should be enough for most cases.
Fabric Workspace Won't Connect
Sign-in popup doesn't appear: Check your internet connection, restart the app, and try again.
MFA prompt closes too quickly: The sign-in flow allows up to 120 seconds. Make sure your authenticator app notifications are enabled, or have your security key ready before starting the connection.
Connected but can't access the workspace: Your Microsoft account may not have the right permissions. You need at least Contributor role on the Fabric workspace.
SSAS/Azure AS on macOS or Linux
The library used to connect to SQL Server Analysis Services and Azure Analysis Services (ADOMD.NET) is Windows-only. If you're on macOS or Linux:
- Microsoft Fabric works on all platforms with no extra setup needed.
- Azure Analysis Services works on all platforms via Azure AD token authentication.
- On-premises SSAS requires Kerberos authentication. See Kerberos Authentication for SSAS for the setup.
Firewall and Proxy
If you're behind a corporate firewall, make sure these endpoints are reachable:
| Endpoint | Purpose |
|---|---|
| Your data source server | Database connections |
*.fabric.microsoft.com |
Fabric workspace connections |
*.analysis.windows.net |
Azure AS and Power BI connections |
login.microsoftonline.com |
Microsoft Entra ID authentication |
api.fact-foundry.com |
License validation |
Connection String Tips
- SQL Server: Use
server\instancefor named instances. Include the port if non-default:server,1433. - PostgreSQL: Cloud-hosted databases usually require SSL. Check the SSL options in the connection dialog.
- Snowflake: Include the region in the account identifier:
account.region.snowflakecomputing.com.
Debug Logs
If you can't figure out what's wrong, the debug logs often have the answer:
- Go to Settings > Debug.
- Click View Debug Logs.
- Look for error entries around the time of the failure.
- You can export logs to a text file to share with support.
Related Microsoft Documentation
| Topic | Link |
|---|---|
| Microsoft Entra ID | Microsoft Entra ID documentation |
| Analysis Services client libraries | ADOMD.NET and client libraries |
| Microsoft Fabric | What is Microsoft Fabric? |