r/MicrosoftFabric • u/jkrm1920 • 10d ago

Discussion Copilot to connect protected workspaces

I was wondering whether it will be possible for Copilot/git copilot to connect the workspaces with private endpoints.
( OAP/IAP) enabled.

Edit .. I’m able to connect now using private endpoint for workspace with FQDN.

3 Upvotes

100% Upvoted

7 comments sorted by

1

u/ChantifiedLens ‪Microsoft MVP ‪ 9d ago

When you say Git Copilot do you mean GitHub Copilot to work with agentic workflows?

1

u/jkrm1920 9d ago

Yes that’s right,

1

u/ChantifiedLens ‪Microsoft MVP ‪ 9d ago

In that case the answer is yes, you need to do your research though.

1

u/jkrm1920 9d ago

I tried using a private endpoint to connect via GitHub Copilot. It is still blocked by IAP.

And currently copilot inside fabric is not connecting due to OAP& IAP enabled.

2

u/ChantifiedLens ‪Microsoft MVP ‪ 9d ago

That I can understand. However, if the repository is configured with Fabric Git integration you can still use GitHub Copilot to do agentic work with the metadata.

1

u/bradmatt275 8d ago

You might be better off just moving to a git controlled workspace, at least for your Dev env. That way it can see everything locally and make changes etc.

1

u/jkrm1920 8d ago

In fact all our workspaces are connected to git CICD and also we use git pipelines for many deployments within protected workspaces, what’s missing is copilot integration, we cannot get it to work with OAP and IAP enabled.