Skip to content

Commit 611998e

Browse files
committed
Add GCM migration
1 parent 81ada70 commit 611998e

File tree

1 file changed

+10
-3
lines changed

1 file changed

+10
-3
lines changed

includes/notification-hubs-firebase-deprecation.md

Lines changed: 10 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5,13 +5,17 @@ title: include file
55
author: sethmanheim
66
ms.service: notification-hubs
77
ms.topic: include
8-
ms.date: 12/06/2023
8+
ms.date: 01/16/2024
99
ms.author: sethm
1010
ms.custom: include file
1111
---
1212

13-
> [!IMPORTANT]
14-
> Firebase Cloud Messaging (FCM) is a service that, among other things, facilitates developers sending push notifications to Google Play-supported Android devices. Azure Notification Hubs currently communicates with FCM using the legacy HTTP protocol. FCM v1 is an updated API that offers more features and capabilities. Google announced that they are deprecating FCM legacy HTTP and will stop supporting it on June 20, 2024. Therefore, developers who use Azure Notification Hubs to communicate with Google Play-supported Android devices today, will need to migrate their applications and notification payloads to the newer format. Azure Notification Hubs will continue to support FCM legacy HTTP until Google stops accepting requests. Once the new FCM integration is complete, Azure Notification Hubs will announce when you can begin migrating. For more information, see the [migration steps](#migration-steps) in the next section.
13+
> [!NOTE]
14+
> The core capabilities for the integration of Azure Notification Hubs (ANH) with Firebase Cloud Messaging (FCM) v1 is ready for testing. As a reminder, Google will stop supporting FCM Legacy HTTP on June 20, 2024, so you must migrate your applications and notification payloads to the new format before then. All methods of onboarding will be ready for migration by March 1, 2024.
15+
>
16+
> To help with this transition, we invite you to join our preview program and test the FCM v1 onboarding process for REST APIs in February 2024. This gives you early access to the new features and capabilities, as well as the opportunity to provide feedback and report any issues.
17+
>
18+
> If you are interested in joining the preview program, [contact us by email](mailto:[email protected]) by January 25, 2024. We will reply with instructions on how to onboard to FCM v1 using the Azure portal or the REST API. You will also receive a link to our documentation and support channels.
1519
1620
## Migration steps
1721

@@ -24,3 +28,6 @@ Firebase Cloud Messaging (FCM) legacy API will be deprecated by July 2024. You c
2428
1. Stop sending notifications to FCM legacy: once you remove all FCM legacy devices, stop sending notifications to FCM legacy. All notifications should be sent exclusively to FCM v1 at this point, and you should be fully migrated.
2529

2630
If you have any questions or issues, contact our support team.
31+
32+
## Integration steps
33+

0 commit comments

Comments
 (0)