Unable to Provision SQL Analytics Endpoint or Retry for Lakehouse

Hi @KritikaSingh,

The SQL analytics endpoint should normally be created automatically when a Lakehouse is created.
If the endpoint is stuck in provisioning and the Retry option also fails, I would treat this as a provisioning/backend issue rather than a normal configuration issue.

Microsoft documents that every Lakehouse has its own SQL analytics endpoint, and the platform is responsible for keeping the endpoint metadata in sync with the Lakehouse.

Reference:
SQL analytics endpoint metadata sync

A few things I would try:

1. Create a new test Lakehouse in the same workspace and check whether the SQL endpoint provisions.
2. Create a new test Lakehouse in another workspace on the same capacity.
3. Check the Fabric support / known issues page to see whether there is an active issue in your region or capacity.
4. If only this Lakehouse is affected, recreate the Lakehouse if it is still empty or early in development.
5. If issue still persist, raise a Microsoft support ticket.

Known issues page:
Microsoft Fabric known issues

There is also a similar community thread where the SQL analytics endpoint did not provision and retry did not resolve the issue. The accepted recommendation was to recreate the Lakehouse, and if the issue persists, raise a Microsoft support ticket with the error details and correlation IDs.

Similar thread:
Unable to Provision SQL Analytics Endpoint or Retry for Lakehouse or Warehouse

When raising the ticket, include the workspace name, Lakehouse name, capacity, region, timestamp, error message, and any correlation/request ID from the failed provisioning attempt. Here is the link for raising a support ticket: https://support.fabric.microsoft.com/en-IN/support/

Best regards,
Solutions Architect · Microsoft Fabric Specialist · Parchitect

💡Did my response help you? Clicking Kudos is a small gesture that goes a long way, it encourages contributors and helps the community thrive!
✔️Did I answer your question? Please mark my post as a Solution, it helps others find the answer faster.

Unless you are going to be updating the data directly on a regular basis you are probably better off just placing all your flat files on OneDrivesnd accessing via PowerQuery and SQL. You will find the lake process too cumbersome and un-necessary.

Hi KritikaSingh.,
Thank you for reaching out to the Microsoft Fabric Community Forum and thanks to Parchitect, and timeseriesIQR  for sharing helpful insights.

Just checking in, were you able to resolve the issue? If not please feel free to share an update and we will be happy to assist further.
Your feedback will also help others facing similar challenges.

Thank you.

Hi KritikaSingh,

Could you please confirm if the issue has been resolved? If not, feel free to reach out if you have any further questions.

Your update would be helpful for other members who may face a similar issue.

Best Regards,

Shivani.

Hi, can you please provide snapshots for reference to understand better 

Thanks