Merge pull request #276793 from vac0224/vc-fcmv1-call-chat-2024-06-04

New FCM v1 Migrate and Register

Author: JamesJBarnett

articles/communication-services/how-tos/calling-sdk/push-notifications.md

@@ -1,5 +1,5 @@
 ---
-title: Enable push notifications for calls.
+title: Enable push notifications for calls
 titleSuffix: An Azure Communication Services how-to guide
 description: Use Azure Communication Services SDKs to enable push notifications for calls.
 author: tophpalmer
@@ -64,3 +64,8 @@ In case that you want to revoke an identity you need to follow [this process](..
 - [Learn how to subscribe to events](./events.md)
 - [Learn how to manage calls](./manage-calls.md)
 - [Learn how to manage video](./manage-video.md)
+
+## Related topics
+
+- [Migrate Android SDK push notifications to FCM v1](../../tutorials/call-chat-migrate-android-push-fcm-v1.md)
+- [Register for Android SDK push notifications using FCM v1](../../tutorials/call-chat-register-android-push-fcm-v1.md)

articles/communication-services/toc.yml

@@ -241,6 +241,10 @@ items:
       href: tutorials/postman-tutorial.md
     - name: Send short URL
       href: tutorials/sms-url-shortener.md
+    - name: Migrate to Android push notifications FCM v1
+      href: tutorials/call-chat-migrate-android-push-fcm-v1.md
+    - name: Register for Android push notifications FCM v1
+      href: tutorials/call-chat-register-android-push-fcm-v1.md
     - name: Phone numbers
       items:
       - name: Port a phone number into Azure

articles/communication-services/tutorials/call-chat-migrate-android-push-fcm-v1.md

@@ -0,0 +1,80 @@
+---
+title: Migrate Android SDK push notifications to FCM v1
+titleSuffix: An Azure Communication Services tutorial
+description: Learn how to migrate Android SDK push notifications from Google Cloud Messaging (GCM/FCM) to Firebase Cloud Messaging (FCM HTTP v1).
+author: jiminwen
+services: azure-communication-services
+ms.author: jiminwen
+ms.date: 05/31/2024
+ms.topic: tutorial
+ms.service: azure-communication-services
+---
+
+# Migrate Android SDK push notifications to Firebase Cloud Messaging HTTP v1 
+
+This article applies to call and chat applications using Android SDK with Firebase Cloud Messaging (FCM) push notification. FCM was previously known as Google Cloud Messaging (GCM/FCM).
+
+On June 20, 2023, Google announced that it [deprecated sending messages using the FCM legacy APIs](https://firebase.google.com/docs/cloud-messaging). Google is removing the legacy FCM from service in June 2024. Google recommends [migrating from legacy FCM APIs to FCM HTTP v1](https://firebase.google.com/docs/cloud-messaging/migrate-v1).
+
+If you have a new Android application or never used Google FCM, see the [Register for Android SDK push notifications using FCM v1](./call-chat-register-android-push-fcm-v1.md) article.
+
+If your Android application uses the push notification feature, complete the following steps to migrate your push notification to FCM HTTP v1.
+
+## 1. Generate a private key in Firebase console
+
+1. Open your project in [Firebase console](https://console.firebase.google.com/).
+
+2. Open **Project settings** > **Service accounts**.
+
+3. Select any programming language.
+
+4. Click **Generate new private key** to download a JSON file containing your new private key.
+
+    ![Screenshot of how to generate new private key for FMC v1 in Firebase console.](./media/call-chat-fcm-firebase-console-gen-key.png)
+
+5. Find and open the downloaded JSON file. You need values from this file for the next step.
+
+
+## 2. Provide the private key credentials for Google (FCM v1)
+
+1. Open your Azure Communication Services Notification Hub in the [Azure portal](https://portal.azure.com).
+
+2. Open **Settings** > **Google (FCM v1)**.
+
+3. Enter the values from your downloaded JSON file in the text boxes for **Private Key**, **Client Email**, and **Project ID**.
+    
+    ![Screenshot of how to provide a new private key credentials for FCM v1 in Azure portal settings.](./media/call-chat-fcmv1-credentials-add.png)
+
+4. Click **Save**.
+
+## 3. Remove legacy credentials for Google (GCM/FCM)
+
+1. Open your Azure Communication Services Notification Hub in the [Azure portal](https://portal.azure.com).
+
+2. Open **Settings** > **Google (GCM/FCM)**.
+
+3. Clear the **API Key** text box.
+    
+    ![Screenshot of how to remove legacy credentials for GCM / FCM from Azure portal settings.](./media/call-chat-fcm-credentials-remove.png)
+
+4. Click **Save**.
+
+## 4. Verify that your application receives push notifications
+
+1. Wait a few minutes for the changes you made at the Notification Hub to take effect.
+Your application might experience duplicate push notifications or missed notifications during this time.
+
+2. Make sure your application receives push notifications without error.
+
+
+## Troubleshooting
+
+If your application can’t receive push notifications, make sure your new FCM v1 credentials are correct. Repeat the steps in this document as needed to [Generate a private key in Firebase console](#1-generate-a-private-key-in-firebase-console) or [Provide the private key credentials for Google (FCM v1)](#2-provide-the-private-key-credentials-for-google-fcm-v1).  
+
+If  your application still can’t receive push notifications, contact Azure Communication Services at [Microsoft Azure Help+ support](https://ms.portal.azure.com/#view/Microsoft_Azure_Support/HelpAndSupportBlade/~/overview).
+
+
+## Related articles
+
+[Enable push notifications in your Android chat app](./chat-android-push-notification.md)
+[Enable push notifications for calls](../how-tos/calling-sdk/push-notifications.md)

articles/communication-services/tutorials/call-chat-register-android-push-fcm-v1.md

@@ -0,0 +1,71 @@
+---
+title: Register for Android SDK push notifications using FCM v1
+titleSuffix: An Azure Communication Services tutorial
+description: Learn how to register for Android SDK push notifications using Google Firebase Cloud Messaging (FCM HTTP v1).
+author: jiminwen
+services: azure-communication-services
+ms.author: jiminwen
+ms.date: 05/31/2024
+ms.topic: tutorial
+ms.service: azure-communication-services
+---
+
+# Register for Android SDK push notifications using Firebase Cloud Messaging HTTP v1 
+
+This article applies to call and chat applications using Android SDK with Firebase Cloud Messaging (FCM) push notification. FCM was previously known as Google Cloud Messaging (GCM/FCM).
+
+On June 20, 2023, Google announced that it [deprecated sending messages using the FCM legacy APIs](https://firebase.google.com/docs/cloud-messaging). Google is removing the legacy FCM from service in June 2024. Google recommends [migrating from legacy FCM APIs to FCM HTTP v1](https://firebase.google.com/docs/cloud-messaging/migrate-v1).
+
+If your existing Android application uses the push notification feature, you need to [migrate to the FCM HTTP v1 endpoint](./call-chat-migrate-android-push-fcm-v1.md).
+
+If you have a new Android application or never used Google FCM, complete the following steps to register for Android SDK push notification using FCM HTTP v1.
+
+Complete the following steps to migrate your push notification to FCM HTTP v1.
+
+## 1. Generate a private key in Firebase console
+
+1. Open your project in [Firebase console](https://console.firebase.google.com/).
+
+2. Open **Project settings** > **Service accounts**.
+
+3. Select any programming language.
+
+4. Click **Generate new private key** to download a JSON file containing your new private key.
+    
+    ![Screenshot of how to generate a new private key for FMC v1 in Firebase console.](./media/call-chat-fcm-firebase-console-gen-key.png)
+
+5. Find and open the downloaded JSON file. You need values from this file for the next step.
+
+
+## 2. Provide the private key credentials for Google (FCM v1)
+
+1. Open your Azure Communication Services Notification Hub in the [Azure portal](https://portal.azure.com).
+
+2. Open **Settings** > **Google (FCM v1)**.
+
+3. Enter the values from your downloaded JSON file in the text boxes for **Private Key**, **Client Email**, and **Project ID**.
+    
+    ![Screenshot of how to provide a new private key credentials for FCM v1 in Azure portal settings.](./media/call-chat-fcmv1-credentials-add.png)
+
+4. Click **Save**.
+
+
+## 3. Verify that your application receives push notifications
+
+1. Wait a few minutes for the changes you made at the Notification Hub to take effect.
+Your application might experience duplicate push notifications or missed notifications during this time.
+
+2. Make sure your application receives push notifications without error.
+
+
+## Troubleshooting
+
+If your application can’t receive push notifications, make sure your new FCM v1 credentials are correct. Repeat the steps in this document as needed to [Generate a private key in Firebase console](#1-generate-a-private-key-in-firebase-console) or [Provide the private key credentials for Google (FCM v1)](#2-provide-the-private-key-credentials-for-google-fcm-v1).  
+
+If  your application still can’t receive push notifications, contact Azure Communication Services at [Microsoft Azure Help+ support](https://ms.portal.azure.com/#view/Microsoft_Azure_Support/HelpAndSupportBlade/~/overview).
+
+
+## Related articles
+
+[Enable push notifications in your Android chat app](./chat-android-push-notification.md)
+[Enable push notifications for calls](../how-tos/calling-sdk/push-notifications.md)

articles/communication-services/tutorials/chat-android-push-notification.md

@@ -235,3 +235,8 @@ If the app is integrated with Azure Function, initialization of application para
       android:name=".MyAppConfiguration"
 >
 ```
+
+## Related topics
+
+- [Migrate Android SDK push notifications to FCM v1](./call-chat-migrate-android-push-fcm-v1.md)
+- [Register for Android SDK push notifications using FCM v1](./call-chat-register-android-push-fcm-v1.md)