Merge pull request #233852 from brianlehr/newbranch

additional comments about ROAs

Author: prmerger-automator[bot]

articles/virtual-network/ip-services/create-custom-ip-address-prefix-cli.md

@@ -110,7 +110,7 @@ The following steps show the steps required to prepare sample customer range (1.
     Use the following command to create a signed message that will be passed to Microsoft for verification.  
    
     > [!NOTE]
-    > If the Validity End date was not included in the original ROA, pick a date that corresponds to the time you intend to have the prefix advertised by Azure.
+    > If the Validity End date was not included in the original ROA, pick a date that corresponds to the time you intend to have the prefix advertised by Azure.  Also note that Microsoft will not stop advertising the range after the specified date, but it is recommended to independently create a follow-up ROA if the original expiration date has passed.
  
     ```powershell
     $byoipauth="xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx|1.2.3.0/24|yyyymmdd"

articles/virtual-network/ip-services/create-custom-ip-address-prefix-portal.md

@@ -60,7 +60,7 @@ To utilize the Azure BYOIP feature, you must perform the following steps prior t
     * After the ROA is complete and submitted, allow at least 24 hours for it to become available to Microsoft, where it will be verified to determine its authenticity and correctness as part of the provisioning process.
 
 > [!NOTE]
-> It is also recommended to create a ROA for any existing ASN that is advertising the range to avoid any issues during migration.
+> It is also recommended to create a ROA for any existing ASN that is advertising the range to avoid any issues during migration.  Also note that Microsoft will not stop advertising the range after the specified date, but it is recommended to independently create a follow-up ROA if the original expiration date has passed.
 
 ### Certificate readiness
 

articles/virtual-network/ip-services/create-custom-ip-address-prefix-powershell.md

@@ -65,7 +65,7 @@ To utilize the Azure BYOIP feature, you must perform the following steps prior t
     * After the ROA is complete and submitted, allow at least 24 hours for it to become available to Microsoft, where it will be verified to determine its authenticity and correctness as part of the provisioning process.
 
 > [!NOTE]
-> It is also recommended to create a ROA for any existing ASN that is advertising the range to avoid any issues during migration.
+> It is also recommended to create a ROA for any existing ASN that is advertising the range to avoid any issues during migration.  Also note that Microsoft will not stop advertising the range after the specified date, but it is recommended to independently create a follow-up ROA if the original expiration date has passed.
 
 ### Certificate readiness