AzureRetirement
Azure Notification Hubs: FCM legacy API support deprecation
The Azure updates record lists Mar 2027 as the retirement date for Firebase Cloud Messaging (FCM) legacy API support in Azure Notification Hubs. The announcement text states that Google stops supporting FCM legacy HTTP on June 20, 2024.
Retires approx., Mar 2027
· The vendor gives a month, not a day.
What breaks
FCM is used to send push notifications to Google Play supported Android devices, and Azure Notification Hubs previously communicated with FCM using the Legacy HTTP protocol. The announcement states that Google stops supporting FCM legacy HTTP on June 20, 2024, and that the FCM legacy API is deprecated by July 2024. It states that all customers must migrate applications and notification payloads to the new format (FCM v1) before June 20, 2024, and asks them to follow the migration steps before 1 June 2024. The announcement text does not mention Mar 2027; that date comes from the Azure updates record.
What to do
Migrate your applications and notification payloads to the new format (FCM v1). The announcement asks customers to follow the FCM v1 migration steps before 1 June 2024. Questions can be posted at Microsoft Q&A: https://aka.ms/anhfcmv1.
Replacement
FCM v1
Sources
- Official sourceazure.microsoft.comOfficial
- Additional sourcegithub.comOfficial
- Additional sourceaka.msOfficial
Last checked against the first source in this list on .
Found an error? Report it
The text on this page is drafted with AI assistance from the vendor's text, checked against the official source and approved by a person before it is published. How items are written
Last checked · Added · Changelog for this item