Skip to content

Commit 0664509

Browse files
committed
Add FCM migration alert
1 parent 04c8afd commit 0664509

6 files changed

+22
-12
lines changed

articles/notification-hubs/android-sdk.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Send push notifications to Android using Azure Notification Hubs and Fire
33
description: In this tutorial, you learn how to use Azure Notification Hubs and Google Firebase Cloud Messaging to send push notifications to Android devices (version 1.0.0-preview1).
44
author: sethmanheim
55
ms.author: sethm
6-
ms.date: 04/23/2024
6+
ms.date: 05/08/2024
77
ms.topic: tutorial
88
ms.service: notification-hubs
99
ms.reviewer: heathertian
@@ -15,8 +15,8 @@ ms.custom: devx-track-csharp
1515

1616
This tutorial shows how to use Azure Notification Hubs and the updated version of the Firebase Cloud Messaging (FCM) SDK (version 1.0.0-preview1) to send push notifications to an Android application. In this tutorial, you create a blank Android app that receives push notifications using Firebase Cloud Messaging (FCM).
1717

18-
> [!NOTE]
19-
> For information about Firebase Cloud Messaging deprecation and migration steps, see [Google Firebase Cloud Messaging migration](notification-hubs-gcm-to-fcm.md).
18+
> [!IMPORTANT]
19+
> As of June 2024, FCM legacy APIs will no longer be supported and will be retired. To avoid any disruption in your push notification service, you must [migrate to the FCM v1 protocol](notification-hubs-gcm-to-fcm.md) as soon as possible.
2020
2121
You can download the completed code for this tutorial from [GitHub](https://github.com/Azure/azure-notificationhubs-android/tree/v1-preview/notification-hubs-test-app-refresh).
2222

articles/notification-hubs/configure-google-firebase-cloud-messaging.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ manager: femila
77

88
ms.service: notification-hubs
99
ms.topic: article
10-
ms.date: 06/30/2023
10+
ms.date: 05/08/2024
1111
ms.author: sethm
1212
ms.reviewer: thsomasu
1313
ms.lastreviewed: 03/25/2019
@@ -17,8 +17,8 @@ ms.lastreviewed: 03/25/2019
1717

1818
This article shows you how to configure Google Firebase Cloud Messaging (FCM) settings for an Azure notification hub using the Azure portal.
1919

20-
> [!NOTE]
21-
> For information about Firebase Cloud Messaging deprecation and migration steps, see [Google Firebase Cloud Messaging migration](notification-hubs-gcm-to-fcm.md).
20+
> [!IMPORTANT]
21+
> As of June 2024, FCM legacy APIs will no longer be supported and will be retired. To avoid any disruption in your push notification service, you must [migrate to the FCM v1 protocol](notification-hubs-gcm-to-fcm.md) as soon as possible.
2222
2323
## Prerequisites
2424

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

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: sethmanheim
55
manager: femila
66
ms.service: notification-hubs
77
ms.topic: article
8-
ms.date: 04/12/2024
8+
ms.date: 05/08/2024
99
ms.author: sethm
1010
ms.reviewer: heathertian
1111
ms.lastreviewed: 04/12/2024
@@ -15,6 +15,9 @@ ms.lastreviewed: 04/12/2024
1515

1616
This article describes the core capabilities for the integration of Azure Notification Hubs with Firebase Cloud Messaging (FCM) v1. 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.
1717

18+
> [!IMPORTANT]
19+
> As of June 2024, FCM legacy APIs will no longer be supported and will be retired. To avoid any disruption in your push notification service, you must [migrate to the FCM v1 protocol](notification-hubs-gcm-to-fcm.md) as soon as possible.
20+
1821
## Concepts for FCM v1
1922

2023
- A new platform type is supported, called **FCM v1**.

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

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: sethmanheim
55
manager: femila
66
ms.service: notification-hubs
77
ms.topic: article
8-
ms.date: 03/01/2024
8+
ms.date: 05/08/2024
99
ms.author: sethm
1010
ms.reviewer: heathertian
1111
ms.lastreviewed: 03/01/2024
@@ -15,7 +15,11 @@ ms.lastreviewed: 03/01/2024
1515

1616
Google will deprecate the Firebase Cloud Messaging (FCM) legacy API 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. This section describes the steps to migrate from FCM legacy to FCM v1 using the Azure SDKs.
1717

18+
> [!IMPORTANT]
19+
> As of June 2024, FCM legacy APIs will no longer be supported and will be retired. To avoid any disruption in your push notification service, you must [migrate to the FCM v1 protocol](notification-hubs-gcm-to-fcm.md) as soon as possible.
20+
1821
## Prerequisites
22+
1923
- Ensure that **Firebase Cloud Messaging API (V1)** is enabled in Firebase project setting under **Cloud Messaging**.
2024
- Ensure that FCM credentials are updated. [Follow step 1 in the REST API guide](firebase-migration-rest.md#step-1-add-fcm-v1-credentials-to-hub).
2125

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

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: sethmanheim
55
manager: femila
66
ms.service: notification-hubs
77
ms.topic: article
8-
ms.date: 05/07/2024
8+
ms.date: 05/08/2024
99
ms.author: sethm
1010
ms.reviewer: heathertian
1111
ms.lastreviewed: 03/01/2024
@@ -15,6 +15,9 @@ ms.lastreviewed: 03/01/2024
1515

1616
The core capabilities for the integration of Azure Notification Hubs with Firebase Cloud Messaging (FCM) v1 are available. 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.
1717

18+
> [!IMPORTANT]
19+
> As of June 2024, FCM legacy APIs will no longer be supported and will be retired. To avoid any disruption in your push notification service, you must [migrate to the FCM v1 protocol](#migration-steps) as soon as possible.
20+
1821
## Concepts for FCM v1
1922

2023
- A new platform type is supported, called **FCM v1**.

articles/notification-hubs/push-notifications-android-specific-devices-firebase-cloud-messaging.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ ms.tgt_pltfrm: mobile-android
99
ms.devlang: java
1010
ms.topic: tutorial
1111
ms.custom: mvc, devx-track-java
12-
ms.date: 02/06/2024
12+
ms.date: 05/08/2024
1313
ms.author: sethm
1414
ms.reviewer: heathertian
1515
ms.lastreviewed: 02/06/2024
@@ -21,8 +21,8 @@ ms.lastreviewed: 02/06/2024
2121

2222
## Overview
2323

24-
> [!NOTE]
25-
> For information about Firebase Cloud Messaging deprecation and migration steps, see [Google Firebase Cloud Messaging migration](notification-hubs-gcm-to-fcm.md).
24+
> [!IMPORTANT]
25+
> As of June 2024, FCM legacy APIs will no longer be supported and will be retired. To avoid any disruption in your push notification service, you must [migrate to the FCM v1 protocol](notification-hubs-gcm-to-fcm.md) as soon as possible.
2626
2727
This tutorial shows you how to use Azure Notification Hubs to broadcast breaking news notifications to an Android app. When complete, you will be able to register for breaking news categories you are interested in, and receive only push notifications for those categories. This scenario is a common pattern for many apps where notifications have to be sent to groups of users that have previously declared interest in them, for example, RSS reader, apps for music fans, etc.
2828

0 commit comments

Comments
 (0)