Update how-to-mfa-server-migration-utility.md

Author: Justinha

articles/active-directory/authentication/how-to-mfa-server-migration-utility.md

@@ -341,9 +341,8 @@ Content-Type: application/json
 
 
 #### Response
->[!NOTE] 
->The response object shown here might be shortened for readability.
-
+>**Note:** The response object shown here might be shortened for readability.
+<!-- {
   "blockType": "response",
   "truncated": true,
   "@odata.type": "microsoft.graph.internalDomainFederation"
@@ -414,12 +413,11 @@ If the upgrade had issues, follow these steps to roll back:
      "federatedIdpMfaBehavior": "enforceMfaByFederatedIdp"
    }
    ```
-
+   
+   The following response object is shortened for readability.
 
    **Response**
 
-   >[!NOTE]
-   >The response object shown here might be shortened for readability.
    <!-- {
      "blockType": "response",
      "truncated": true,
@@ -452,6 +450,7 @@ If the upgrade had issues, follow these steps to roll back:
 
 Users will no longer be redirected to your on-premises federation server for MFA, whether they’re targeted by the Staged Rollout tool or not. Note this can take up to 24 hours to take effect.
 
+
 ## Next steps
 
 - [Overview of how to migrate from MFA Server to Azure AD Multi-Factor Authentication](how-to-migrate-mfa-server-to-azure-mfa.md)