MCM - Update AHB FAQ for expiration notifications

Author: bandersmsft

articles/cost-management-billing/scope-level/faq-azure-hybrid-benefit-scope.yml

@@ -8,7 +8,7 @@ metadata:
   ms.service: cost-management-billing
   ms.subservice: ahb
   ms.topic: faq
-  ms.date: 10/12/2023
+  ms.date: 07/01/2024
   ms.author: banders
 title: Centrally managed Azure Hybrid Benefit FAQ
 summary: |
@@ -55,7 +55,7 @@ sections:
       - question: What happens after I set the license assignment review date?
         answer: |
           After you assign a license and set a review date, the license assignment automatically expires 90 days after the review date. The license assignment becomes inactive and no longer applies 90 days after expiration.
-          
+
           Microsoft sends email notifications:
 
           - Ninety days before expiration
@@ -70,6 +70,18 @@ sections:
           4. Fill the review date and select **Save**.
 
           No notification is sent on the review date. 
+      - question: Who gets expiration notifications?
+        answer: | 
+        Expiration notification emails are sent 30 days before expiration and again on the expiration date. The sending email address is `[email protected]`. You might want to add the email address to your safe senders or allowlist.
+
+          Emails are sent to different people depending on your purchase method:
+
+          - Customers with EA subscriptions
+              - Notifications are sent to the EA notification contacts, EA admin, reservation owners, and the reservation administrator.
+          - Customers with Microsoft Customer Agreement (Azure Plan)
+              - Notifications are sent to the reservation owners and the reservation administrator.
+          - Cloud Solution Provider and new commerce partners
+              - Emails are sent to the partner notification contact.
       - question: Can I use the new experience with self-installed SQL Server in Azure virtual machines?
         answer: |
           The new approach of centrally managing Azure Hybrid Benefit at a scope-level supports SQL Server in Azure Virtual machines. However, it’s essential that you have enabled automatic registration of the self-installed SQL server images with the IaaS extension *before* you assign SQL licenses. The experience includes a feature that informs you about current usage of Azure Hybrid Benefit. And, the usage of SQL licenses that aren’t discounted. Assigning the number of SQL Server licenses at the level of the current usage ensures that you don't experience unexpected pay-as-you-go charges. Because the unregistered SQL VMs aren’t recognized as SQL resources, registering them with the IaaS extension *after* you begin assigning licenses at a scope-level could lead to the license assignments being insufficient to cover the newly recognized SQL VMs. In that case, those *new* SQL VMs from registration might incur unexpected pay-as-you-go charges.