JulianPayne_i4
7 years agoFrequent Visitor
Status:
Needs Votes
Cannot use APIs for Data Refresh in PBIS
We are using APIs in PBIX to get data and the refreshes work. When we upload to PBIS to run and refresh out models in the cloud, the same APIs and M Queries do not work for all our APIs, specifically those with multiple query parameters in the APIS. We are an ISV and we want to have multi-tenant (workspace) architecture and refresh our models multiple times a day. We need APIs on scheduled refresh. Some APIs work (we had to put all relative paths in the main URL), but some cannot connect based on security/truest authentication. Please have the engineering team review API protocols in PBIS. Thank you.
1 Comment
- fbcideas_migusrNew MemberStatus added:Needs Votes
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...tmihara24 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 ...PeterDaniels7 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...TeemuMultanen8 hours agoAdvocate INew296Views47likes2Comments