Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Azure SDK limitation while fetching app registrations. #11817

Closed
ietashish opened this issue Jun 4, 2020 · 3 comments
Closed

Azure SDK limitation while fetching app registrations. #11817

ietashish opened this issue Jun 4, 2020 · 3 comments
Assignees
Labels
customer-reported Issues that are reported by GitHub users external to the Azure organization. Graph Mgmt This issue is related to a management-plane library. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention Workflow: This issue is responsible by Azure service team.

Comments

@ietashish
Copy link

Our requirement is to list all the registered applications for a tenant. The response should also contain information about the owners of the application.

To do so, we currently had to resort to calling Graph REST API natively instead of using Python SDK API.
The Graph REST API allows us to pass 'expand' parameter OData query parameters while calling API. So by calling,

GET /applications?$expand=Owners

we are effectively able to expand and join ‘Owners’ information with ‘application’.

The 'expand' parameter allows us to get owners of the application within the same API call. Without this we have to make one more API call to get owner for each application (once we have the list of applications from first API call) which is very time consuming.

However no such provision to pass ‘expand’ parameter exists in equivalent method in Python SDK. The API we would like to use is this one.
Strangely many other SDK methods for other Azure resources do provide provision for passing expand parameter but is missing from ‘list applications’.

@ghost ghost added needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. customer-reported Issues that are reported by GitHub users external to the Azure organization. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Jun 4, 2020
@kaerm kaerm added the Graph label Jun 4, 2020
@ghost ghost removed the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Jun 4, 2020
@kaerm kaerm added Mgmt This issue is related to a management-plane library. Service Attention Workflow: This issue is responsible by Azure service team. labels Jun 4, 2020
@kaerm
Copy link
Contributor

kaerm commented Jun 4, 2020

@ietashish thanks for reaching out, @nickzhums could you help out here

@nickzhums
Copy link
Contributor

@RodgeFu to double check if python sdk misses this functionality

openapi-sdkautomation bot pushed a commit to AzureSDKAutomation/azure-sdk-for-python that referenced this issue Nov 26, 2020
Aggregated swagger changes k8connect (Azure#11817)

* aggregated swagger changes k8conect

* prettier fix

Co-authored-by: Siri Teja Reddy Kasireddy <sikasire@microsoft.com>
@lmazuel
Copy link
Member

lmazuel commented May 7, 2021

Azure AD Graph API is now deprecated. We do not support SDK fixes to this product anymore. Please refer to this issue for additional way to get support to move to Microsoft Graph API:
azure-deprecation/dashboard#60

@lmazuel lmazuel closed this as completed May 7, 2021
@github-actions github-actions bot locked and limited conversation to collaborators Apr 12, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
customer-reported Issues that are reported by GitHub users external to the Azure organization. Graph Mgmt This issue is related to a management-plane library. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention Workflow: This issue is responsible by Azure service team.
Projects
None yet
Development

No branches or pull requests

6 participants