The argument name to determine Application should be ObjectId instead of ApplicationId

[watahani]

Current behavior

To get an application, we need to provide objectId but argument name is "ApplicationId"

Get-MgApplication -ApplicationId 03dc4a88-bc57-4da0-9d7d-cee2b98fba78

Id                                   DisplayName  AppId                                SignInAudience PublisherDomain
--                                   -----------  -----                                -------------- ---------------
03dc4a88-bc57-4da0-9d7d-cee2b98fba78 testtesttest 50fc07ef-3afd-4df3-8577-a2115c95a0d2 AzureADMyOrg   04.wahaniya.com

Expected

The argument name should be ObjectId.

Get-MgApplication -ObjectId 03dc4a88-bc57-4da0-9d7d-cee2b98fba78

Id                                   DisplayName  AppId                                SignInAudience PublisherDomain
--                                   -----------  -----                                -------------- ---------------
03dc4a88-bc57-4da0-9d7d-cee2b98fba78 testtesttest 50fc07ef-3afd-4df3-8577-a2115c95a0d2 AzureADMyOrg   04.wahaniya.com

[peombwa]

This is by design. For my Microsoft Graph PowerShell SDK, all id parameters are named based on the entity they represent as described in the OpenAPI document e.g. Application entity will have a parameter of ApplicationId.

We understand that customers upgrading from AzureAD Graph can find it confusing to have an appId property and -ApplicationId parameter. In this case, we can consider aliasing -ApplicationId parameter to something like -ObjectId or -Id (If feasible).

cc/ @darrelmiller

[peombwa]

Closing as duplicate of #906.