views created in lakehouse auto generated Analytics endpoint don't show up in GIT repository

[grassdan]

• Scenario: User creates views in lakehouse SQL analytics endpoint
• Expected: Views appear in git sync like standalone warehouse objects do
• Actual: Views are invisible to git — no version control, no deployment path
• Impact: Production dependencies on untracked SQL objects; workspace recovery from git would be incomplete

Then when I make changes those don't show up in GIT so I can't roll back the changes I have to remember what the original was. if I create a separate warehouse it works correctly.

[v-karpurapud]

Hi @grassdan 

Could you please confirm if you've submitted this as an idea in the Ideas Forum? If so, sharing the link here would be helpful for other community members who may have similar feedback.

Best Regards, 
Community Support Team.

[grassdan]

If everyone on the team has development experience this would work but with a team like mine where it is a lot of Business Analysts that don't have experience with GIT we are going to have multiple people doing things from the UI so what ends up happening is I have to look at what the different individuals are doing and convert it over to processes like this and spend the time training people how to do code based work. so it starts breaking the self service model we are trying to do.

[v-karpurapud · Accepted solution]

Hi @grassdan 

We understand that, given your scenario, this remains challenging, even if the existing Idea is implemented in the future, mixed‑skill teams may still face governance and change‑tracking concerns.

At present, there is no alternative supported approach to address this gap. As a next step, we recommend adding a comment to the existing Ideas forum request explaining how UI‑based changes by Business Analysts create governance, audit and tracking challenges in real‑world self‑service environments. This additional context will help ensure the scenario is clearly visible to the product team.

If you feel the current Idea does not fully capture your requirements, you may also consider submitting a separate idea in Fabric Ideas - Microsoft Fabric Community that more precisely reflects your self‑service and mixed‑persona use case.
 

Regards,

Microsoft Fabric Community Support Team

[grassdan]

I did an upvote on that idea, I think it encapsulates the root problem.

[GilbertQ]

Hi @grassdan 

The reason that this happens is that it is an underlying lake house with a SQL analytics endpoint and by default there are no views in an endpoint. It is a read only endpoint and that is why if you create a warehouse you then can see these views because this is a SQL based system.

[grassdan]

the issue is more that one of the primary reasons to use GIT is so that you have a history of everything that has happened and can revert changes, but this allows a change to happen that does not show up in GIT and so there could be a behaviour change in reporting or others and if you are relying on GIT to help you troubleshoot this is a big miss, I don't know of any other place in a development lifecycle that changes are not recorded in GIT. if it is truly a read only endpoint then why am I allowed to make changes to it by adding views, btw that could be the bug the fact that I am able to add views here.

[v-karpurapud]

Hi @grassdan 

Thank you for reaching out to the Microsoft Fabric community forum.
 

Currently, SQL views created in a Lakehouse SQL Analytics Endpoint are not tracked in source control (Git) and are not included in deployment pipelines. 

This is a platform limitation, not a configuration error. Many community members have encountered the same issue, particularly when semantic models rely on Lakehouse SQL views
Lakehouse git integration and deployment pipelines - Microsoft Fabric | Microsoft Learn  
Source control not supporting SQL Analytics endpoi... - Microsoft Fabric Community. 

As of now, there is no supported method for Git tracking or pipeline deployment of these objects.

There is an existing Ideas forum submission requesting support for synchronizing Lakehouse SQL Analytics Endpoint views with Git and deployment pipelines. Include views from Lakehouse SQL Analytics Endpoin... - Microsoft Fabric Community, and you can upvote the idea and follow community discussions for updates.
 

If you have any further questions, feel free to reach out and we'll be glad to assist.
 

Regards,

Microsoft Fabric Community Support Team.
 

[v-karpurapud]

Hi @grassdan 

Just checking in as we haven't received a response to our previous message. Were you able to review the information above? Let us know if you have any additional questions.

Thank You.

[Murtaza_Ghafoor]

@grassdan
 

Fabric DevOps Workaround (Lakehouse Views)
  

Since Lakehouse SQL endpoint views are not tracked in Git, the best practice is:  

Treat views as code – store all CREATE/ALTER VIEW scripts in Git.  
Deploy via pipelines – Azure DevOps to execute SQL scripts.  
Parameterize environments – handle Dev/Test/Prod using variables.  
Use Git for versioning – rollback = revert + redeploy.  
Avoid UI-based changes – always deploy from source control.  

Key Idea:  
Don’t rely on Lakehouse for version control—make Git your single source of truth and deploy everything via pipelines.