Lack of Support for FCMv1 Credentials in Microsoft.NotificationHubs ARM/Bicep Template

[SylberG]

Description: As of June 2024, Google has deprecated support for Google Cloud Messaging (GCM) and Firebase Cloud Messaging (FCM) in favor of FCMv1. However, the Microsoft.NotificationHubs ARM template currently does not include support for configuring FCMv1 credentials. This is now a challenge for users seeking to transition to FCMv1 for push notifications via ARM/Bicep templates.

Question: Is there a plan to update the Microsoft.NotificationHubs ARM/Bicep template to include support for FCMv1 credentials? If so, what is the estimated timeline for this update?

Link to the latest version of the ARM/Bicep template with the existing properties supported : https://learn.microsoft.com/en-us/azure/templates/microsoft.notificationhubs/2017-04-01/namespaces/notificationhubs?pivots=deployment-language-bicep

I have also opened this issue/request in the 'Azure Notification Hub DotNet' GitHub project, not quite sure where to place this request. (https://github.com/Azure/azure-notificationhubs-dotnet/issues/310)

[ManoharLakkoju-MSFT]

@SylberG Thanks for your feedback! We will investigate and update as appropriate.

[SylberG]

@SylberG Thanks for your feedback! We will investigate and update as appropriate.

Could you provide an update on the status of the 'fcmV1Credential' resource? I've noticed it's included in the 'Microsoft.NotificationHubs namespaces/notificationHubs 2023-10-01-preview' pre-release version. Given the approaching deadline for Google's discontinuation of GCM support on June 20, 2024, when can we expect the stable endpoint to be released?

[tfitzmac]

@SylberG - the template reference docs reflect the properties that are defined through the REST API specification. I would suggest creating an issue at https://github.com/Azure/azure-rest-api-specs/tree/main/specification/notificationhubs or https://feedback.azure.com/d365community/forum/405a1b30-8b26-ec11-b6e6-000d3a4f0789