nicholasmisawo
8 months agoRegular Visitor
Status:
New
Support GitHub App authentication for Git integration
Git integration currently only supports PATs, which is not suitable for enterprise-scale use cases
1 Comment
- cllNew MemberThis is a fairly important need for feature parity with Azure DevOps. Being forced to use user PAT tokens is not best practice as you're more likely to run into API rate limits, it's tied to a user account so if they leave it breaks, syncs have that same user as if they made those changes and yes you can use a machine account instead but that requires a license in GitHub. Also, with automation, a user account PAT can sometimes produce false positives with the GitHub API. I've seen this happen several times when using a PAT over a GitHub app with Terraform.
Recent ideas
Allow NotebookUtils getSecret() to authenticate with Workspace Identity
Current behavior In Microsoft Fabric, notebookutils.credentials.getSecret() authenticates against Azure Key Vault using the identity of the user who executes the notebook. This behavior appli...tmihara46 minutes agoNew MemberNew15Views1like1CommentAllow us to rename fabric data agents published to m365
If we use deployment pipelines to promote fabric data agents between dev, test/UAT, and prod fabric workspaces, we need to keep the name of the fabric agent the same in each workspace. If we want to ...PeterDaniels8 hours agoAdvocate IIINew184Views0likes2CommentsMake workspace and item session persistence optional
Description The new persistent session behavior in Microsoft Fabric should be optional rather than forced. Currently, Fabric remembers the workspaces and items that were open in my previous session...TeemuMultanen9 hours agoAdvocate INew297Views47likes2Comments