connectedk8s - move to microsoft graph from the legacy aad graph call

[bganapa]

Describe the bug

Azure AD graph is on the path of deprecation. Microsoft Graph should be used for the graph calls
https://devblogs.microsoft.com/microsoft365dev/microsoft-graph-or-azure-ad-graph/

code path -

azure-cli-extensions/src/connectedk8s/azext_connectedk8s/custom.py

Line 2185 in 066fc43

sub_filters.append("displayName eq '{}'".format("Custom Locations RP"))

Related command

az connectedk8s enable-features -n balacluster2 -g baladelete2 --features cluster-connect custom-locations --debug

This is making the following graph call
urllib3.connectionpool: https://graph.windows.net:443 "GET /72f988bf-86f1-41af-91ab-2d7cd011db47/servicePrincipals?$filter=displayName%20eq%20%27Custom%20Locations%20RP%27&api-version=1.6 HTTP/1.1" 200 1246

Errors

No errors in Azure.

Issue script & Debug output

urllib3.connectionpool: https://graph.windows.net:443 "GET /72f988bf-86f1-41af-91ab-2d7cd011db47/servicePrincipals?$filter=displayName%20eq%20%27Custom%20Locations%20RP%27&api-version=1.6 HTTP/1.1" 200 1246

Expected behavior

N/A

Environment Summary

N/A

Additional context

The issue happens in disconnected clouds where only the latest Microsoft Graph is supported

[yonzhan]

Thank you for opening this issue, we will look into it.

[bganapa]

@SaurabhSharma-MSFT Are you planning to fix this? If yes, could you pls provide any ETA?

[ghost]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @akashkeshari.

Issue Details

---

Describe the bug

Azure AD graph is on the path of deprecation. Microsoft Graph should be used for the graph calls
https://devblogs.microsoft.com/microsoft365dev/microsoft-graph-or-azure-ad-graph/

code path -

azure-cli-extensions/src/connectedk8s/azext_connectedk8s/custom.py

Line 2185 in 066fc43

sub_filters.append("displayName eq '{}'".format("Custom Locations RP"))

Related command

az connectedk8s enable-features -n balacluster2 -g baladelete2 --features cluster-connect custom-locations --debug

This is making the following graph call
urllib3.connectionpool: https://graph.windows.net:443 "GET /72f988bf-86f1-41af-91ab-2d7cd011db47/servicePrincipals?$filter=displayName%20eq%20%27Custom%20Locations%20RP%27&api-version=1.6 HTTP/1.1" 200 1246

Errors

No errors in Azure.

Issue script & Debug output

urllib3.connectionpool: https://graph.windows.net:443 "GET /72f988bf-86f1-41af-91ab-2d7cd011db47/servicePrincipals?$filter=displayName%20eq%20%27Custom%20Locations%20RP%27&api-version=1.6 HTTP/1.1" 200 1246

Expected behavior

N/A

Environment Summary

N/A

Additional context

The issue happens in disconnected clouds where only the latest Microsoft Graph is supported

Author:	bganapa
Assignees:	-
Labels:	bug, Service Attention, Connected Kubernetes, Auto-Assign
Milestone:	-

[mbashtovaya]

@yonzhan Could you provide an ETA for this issue? We are getting flagged by AAD Team as they asked all users to migrate to MS Graph in Sept 2023.

[microsoft-github-policy-service]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @akashkeshari.

[jiasli]

The main CLI has provided a lightweight GraphClient to call Microsoft Graph API. The extension owner of connectedk8s can follow https://github.com/Azure/azure-cli/blob/dev/doc/microsoft_graph_client.md to migrate to Microsoft Graph.