Merge pull request #264218 from sethmanheim/nh1-25

Update FCM migration steps

Author: Court72

articles/notification-hubs/notification-hubs-gcm-to-fcm.md

@@ -5,10 +5,10 @@ author: sethmanheim
 manager: femila
 ms.service: notification-hubs
 ms.topic: article
-ms.date: 12/06/2023
+ms.date: 01/25/2024
 ms.author: sethm
 ms.reviewer: heathertian
-ms.lastreviewed: 04/10/2019
+ms.lastreviewed: 01/25/2024
 ---
 
 # Azure Notification Hubs and Google Firebase Cloud Messaging migration

includes/notification-hubs-firebase-deprecation.md

@@ -5,26 +5,37 @@ title: include file
  author: sethmanheim
  ms.service: notification-hubs
  ms.topic: include
- ms.date: 01/16/2024
+ ms.date: 01/25/2024
  ms.author: sethm
  ms.custom: include file
 ---
 
+The core capabilities for the integration of Azure Notification Hubs with Firebase Cloud Messaging (FCM) v1 are 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.
+
+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. The preview gives you early access to the new features and capabilities, as well as the opportunity to provide feedback and report any issues.
+
+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.
+
+## Concepts for FCM v1
+
+- A new platform type will be supported, called **FCM v1**.
+- New APIs, credentials, registrations, and installations will be used for FCM v1.
+
 > [!NOTE]
-> The core capabilities for the integration of Azure Notification Hubs (ANH) with Firebase Cloud Messaging (FCM) v1 are 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.
->
-> 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.
->
-> 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.
+> The existing FCM platform is referred to as *FCM legacy* in this article.
 
-## Migration steps
+## Migration steps (preview)
 
-Firebase Cloud Messaging (FCM) legacy API will be deprecated by July 2024. You can begin migrating from the legacy HTTP protocol to FCM v1. You can start the migration process by March 1, 2024, and you must complete the migration by June 2024. To migrate from FCM legacy to FCM v1, follow these steps:
+The Firebase Cloud Messaging (FCM) legacy API will be deprecated by July 2024. You can begin migrating from the legacy HTTP protocol to FCM v1 on March 1, 2024. You must complete the migration by June 2024.
 
-1. Migrate credentials to FCM v1: enter your FCM v1 credentials to set up notifications. You can find the [instructions on how to do this here](/azure/notification-hubs/configure-notification-hub-portal-pns-settings?tabs=azure-portal#google-firebase-cloud-messaging-fcm).
-1. Update your client app to start registering as FCMv1 devices: once you're ready to start supporting FCMv1 devices, update your client app so that any new devices start registering as FCM v1 instead of the legacy. When existing FCM legacy registrations expire, they are re-registered as FCM v1. This update ensures that notifications are sent to users appropriately, once the FCM legacy is deprecated.
-1. Delete the FCM legacy registrations: once the FCM v1 registrations are created, delete the corresponding records from the FCM legacy. This prevents duplicate notifications from being sent to your users if you use both APIs. Duplicate notifications can occur and be sent to users if FCM legacy registrations are not deleted.
-1. Update the server app to send notifications to FCM v1: once you complete the previous steps, you can start sending notifications using the new API.
-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.
+> [!IMPORTANT]
+> No action is required at this time; you can check back here for further instructions.
 
 If you have any questions or issues, contact our support team.
+
+To migrate from FCM legacy to FCM v1, here's what you can expect:
+
+1. Provide credentials for FCM v1: you must provide your FCM v1 credentials to set up notifications.
+1. Update the client app to start registering as FCM v1 devices: once you're ready to start supporting FCMv1 devices, update your client app so that any new devices start registering as **FCM v1** instead of **FCM legacy**. This ensures that notifications are sent to users appropriately once FCM legacy is deprecated.
+1. Update the server app to send notifications to FCM v1: once you complete the previous steps, you can start sending notifications using the new API.
+1. Stop sending notifications to FCM legacy: once all existing devices are registered as FCM v1 devices, stop sending notifications to FCM legacy. You should send all notifications exclusively to FCM v1 at this point, and you should be fully migrated.