Additional tooling support to backfill client-provided keys (like uniqueName)

[dkershaw10]

Is your feature request related to a problem? Please describe.

While there are tools that enable this backfilling of existing objects (so that they can be referenced via the existing keyword or updated in Bicep files), there are other options that might be more familiar for customers to use

Describe the solution you'd like

• Primary tooling: Az powershell: -AzAD cmdlets, needs to expose the client provided key
  • For large scale tooling
• Secondary tooling: Entra Portal
  • For clients that has admins only with portal knowledge if/when we don’t have write access to groups

[jikuja]

TYVM for converting feedback quick to issue.

Looks like Portal already support uniqueName:

It's immutable after first write in the UX like it is on the API.

[dkershaw10]

Yeah - that's great for groups.
But unfortunately, uniqueName is not exposed for applications (neither in the properties nor in the Microsoft Graph application manifest).

OK - I discovered that it's "partially" supported in the app manifest. If you open the app manifest you won't see uniqueName there. However, you can add an entry for uniqueName and it's value into the JSON, and save it. This will push the update to the app object. If you re-open the app manifest you still won't see it, but it is written to the object (you can check in Graph Explorer).

[dkershaw10]

@jikuja Looks like the Groups Portal UX has changed. I don't see uniqueName any more. Following up...