Incorp more feedback

Author: sethmanheim

articles/notification-hubs/firebase-migration-rest.md

@@ -59,9 +59,23 @@ Go to your notification hub on the Azure portal, and select **Settings > Google
 
 See the [description of a NotificationHub FcmV1Credential.](/rest/api/notificationhubs/notification-hubs/create-or-update?view=rest-notificationhubs-2023-10-01-preview&tabs=HTTP#fcmv1credential).
 
+- Use API version: 2023-10-01-preview
+- **FcmV1CredentialProperties**:
+
+  |     Name           |     Type      |
+  |--------------------|---------------|
+  |     `clientEmail`    |     string    |
+  |     `privateKey`     |     string    |
+  |     `projectId`      |     string    |
+
 #### Option 3: Update FcmV1 credentials via data plane hub operation
 
-See [Create a notification hub](/rest/api/notificationhubs/create-notification-hub) and [Update a notification hub](/rest/api/notificationhubs/update-notification-hub). Make sure to put **FcmV1Credential** after **GcmCredential**, as the order is important. For example:
+See [Create a notification hub](/rest/api/notificationhubs/create-notification-hub) and [Update a notification hub](/rest/api/notificationhubs/update-notification-hub).
+
+- Use API version: 2015-01
+- Make sure to put **FcmV1Credential** after **GcmCredential**, as the order is important.
+
+For example, the following is the request body:
 
 ```xml
 <NotificationHubDescription xmlns:i='http://www.w3.org/2001/XMLSchema-instance' 
@@ -175,6 +189,14 @@ Use this procedure to test notifications prior to option 2, 3, or 4. See [Notifi
 > [!NOTE]
 > Use API version: 2023-10-01-preview.
 
+In the header:
+
+|     Request header                   |     Value                             |
+|--------------------------------------|---------------------------------------|
+|     `Content-Type`                     |     `application/json;charset=utf-8`    |
+|     `ServiceBusNotification-Format`    |     Set to `fcmV1` or `template`          |
+|     `Servicebusnotification-Tags`      |     {single tag identifier}           |
+
 Test a payload [with the following structure](https://firebase.google.com/docs/reference/fcm/rest/v1/projects.messages/send) via debug send. Note that FcmV1 introduces a significant change in the structuring of the JSON message payload:
 
 1. The entire payload moved under a message object.

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

@@ -13,7 +13,7 @@ ms.lastreviewed: 03/01/2024
 
 # Azure Notification Hubs and Google Firebase Cloud Messaging migration
 
-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.
+The core capabilities for the integration of Azure Notification Hubs with Firebase Cloud Messaging (FCM) v1 are avaiable. 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.
 
 ## Concepts for FCM v1
 
@@ -22,7 +22,7 @@ The core capabilities for the integration of Azure Notification Hubs with Fireba
 
 ## Migration 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.
+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 now. You must complete the migration by June 2024.
 
 - For information about migrating from FCM legacy to FCM v1 using the Azure SDKs, see [Google Firebase Cloud Messaging (FCM) migration using SDKs](firebase-migration-sdk.md).
 - For information about migrating from FCM legacy to FCM v1 using the Azure REST APIs, see [Google Firebase Cloud Messaging (FCM) migration using REST APIs](firebase-migration-rest.md).