Millicent Achieng

@baywet Yes, thanks for the additional info.

Should we also consider having a list of entity types to expand in the settings?

@RabebOthmani Nudging you to provide more information about this issue.

The PowerShell command for the query, which would be `Get-MgOrganizationBrandingLocalization -OrganizationId $organizationId`, is not available on PowerShell SDK. This is not a bug but a limitation of the PowerShell SDK.

@adhiambovivian, @RabebOthmani PowerShell snippets for the following paths are now being generated - https://graph.microsoft.com/v1.0/identityProtection/riskyUsers?$filter=riskLevel eq 'high' - https://graph.microsoft.com/v1.0/identityProtection/riskDetections These are not supported for PowerShell only - https://graph.microsoft.com/v1.0/me/transitiveMemberOf/microsoft.graph.group?$count=true - https://graph.microsoft.com/v1.0/me/calendarview -...

Meanwhile, we do have this [ticket](https://github.com/microsoftgraph/microsoft-graph-devx-api/issues/1047) on DevX API that will enable us to specify which paths, entities or singletons to skip for PowerShell only without affecting other Open API...

@darrelmiller Can we use the `privilegeLevel` property to order the permissions in the 'Higher privileged Permissions' column?

Schema annotations are not included in the resulting EdmModel after parsing the CSDL. Issue raised in the OData lib https://github.com/OData/odata.net/issues/2530

After a review of our codebase, we exclusively use the `System.Security.Cryptography` library and the `SHA-256` algorithm, which adhere to FIPS compliance requirements. If you have any evidence or concerns indicating...

Resolving references is not the solution we are looking for. The `OpenApiReferenceResolver` replaces a reference with its populated object equivalent. More details [here](https://github.com/microsoftgraph/microsoft-graph-devx-api/issues/1144#issuecomment-1418569316).