Hi,
The Jamf Pro connector only supports basic authentication.
With Jamf Pro version 11.5.x basic authentication is no longer supported. Can support for API tokens please be supported?
Thanks
Will
3 Comments
- adams_mgNew Member
+1 to this! Being able to set up an API role for PowerBI reporting and assign an API client ID and API client secret would be a big win for my org's usage needs.
- fbcideas_migusrNew MemberStatus added:New
- miguel
Community Admin
Status changed:NewtoAbandonedThe Jamf connector is not owned by the Microsft team. Instead, it is owned by Jamf. Please route this feedback directly to the Jamf team at [email protected]
Recent ideas
Allow 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 ...PeterDaniels40 minutes agoAdvocate IIINew176Views0likes2CommentsMake 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...TeemuMultanen1 hour agoAdvocate INew292Views47likes2CommentsSupport Encrypted Sensitivity-Labeled Excel Files in Power Query
Description Currently, Power Query Online and Power Query in Excel are unable to access encrypted Excel files. Excel files with sensitivity types other than Public or Non-Business can be encrypted a...ewarstdhyjugkhi2 hours agoMicrosoft EmployeeNew16Views6likes0CommentsAuto-propagate Lakehouse (Direct Lake) permissions to users assigned to a Power BI App audience
Problem When a Power BI report uses a Live Connection to a Direct Lake Semantic Model, end users must have explicit ReadAll / ReadData permissions on the underlying Lakehouse (or its SQL analytics e...majofv4 hours agoNew MemberNew5Views1like0Comments