What causes FIPSModeIsNotSupport?

FIPS 140-2 compliance mode is enforced on the self-hosted integration runtime machine. The Azure Blob connector requires the MD5 algorithm, which cannot operate when FIPS mode is active. The FIPS policy is set via the VM configuration or Group Policy

How do I fix FIPSModeIsNotSupport?

In the self-hosted integration runtime install directory, open the file diawp.exe.config.. Add or modify the enforceFIPSPolicy element to disable FIPS policy for the runtime process.. Follow the configuration guidance in the Microsoft docs to enable FIPS-compatible mode: https://learn.microsoft.com/dotnet/framework/configure-apps/file-schema/runtime/enforcefipspolicy-element.. Note: Windows does not recommend enabling FIPS mode — consider whether it is strictly required by your security policy.

Medium severitydata source

Power BI Refresh Error:
FIPSModeIsNotSupport

What does this error mean?

FIPS mode on the integration runtime blocks the Azure Blob connector, which requires MD5 (non-FIPS). Fix: edit diawp.exe.config in the IR install directory.

Common causes

1FIPS 140-2 compliance mode is enforced on the self-hosted integration runtime machine
2The Azure Blob connector requires the MD5 algorithm, which cannot operate when FIPS mode is active
3The FIPS policy is set via the VM configuration or Group Policy

How to fix it

1In the self-hosted integration runtime install directory, open the file diawp.exe.config.
2Add or modify the enforceFIPSPolicy element to disable FIPS policy for the runtime process.
3Follow the configuration guidance in the Microsoft docs to enable FIPS-compatible mode: https://learn.microsoft.com/dotnet/framework/configure-apps/file-schema/runtime/enforcefipspolicy-element.
4Note: Windows does not recommend enabling FIPS mode — consider whether it is strictly required by your security policy.

Beyond the docs

Common practitioner solutions not covered in the official documentation.

1Restart the self-hosted integration runtime service after editing diawp.exe.config

Frequently asked questions

Does this error affect multiple datasets at once?

If multiple datasets connect to the same data source, yes — all of them will fail until the source connectivity is restored.

Can this error be caused by a server migration or rename?

Yes — if the server name, database name, or connection string changed (e.g., during a cloud migration), Power BI still holds the old connection details. Update the connection in Power BI Desktop and republish.

Does this error appear in Power BI Desktop?

Sometimes — if you open the .pbix file and attempt a refresh, Desktop will surface the same connection error. This is useful for debugging without affecting the Service dataset.

Will the error resolve automatically once the source is back online?

Only if it was a temporary outage. The next scheduled refresh will succeed automatically. If the connection string changed or credentials expired, manual intervention is needed.

Source · learn.microsoft.com/en-us/fabric/data-factory/connector-troubleshoot-azure-blob-storage