Advanced breaking change notice for applications and groups Bicep types

[dkershaw10]

Folks,

Initially we wanted to be a bit more consistent with ARM types, where name represents the unique name identifier, but we think this mapping is causing more confusion. when it's mapped to something else in the API (as seen in groups resource with existing keyword · Issue #39 and Existing on Office 365 groups · Issue #61). So we're renaming the applications and groups Bicep types' name property to uniqueName to be consistent with the Graph API schema.

We'll roll out a new Bicep version, which will have these changes. Once released, please update to use the new Bicep version in VS Code, and make the updates in your Bicep template files. The Graph Bicep extension service will continue to support existing Bicep template files that contain the name property (for applications and groups) for two weeks after the new Bicep version is made available.

NOTE: After the two weeks, the service will only support uniqueName, and any existing files that have not been updated will fail deployments.

[slavizh]

ok. sounds reasonable to me. Would this apply to other resources as well in the future part of the graph or currently will be only for applications and groups and some others that might fall in the same category?

[dkershaw10]

I think we will adopt this pattern (moving forward) for any new Graph types that we add. We have internal guidelines for teams to add a client provided key called uniqueName if the Graph resource doesn't already have a client provided key.