Merge pull request #208874 from Juliako/patch-19

Update connect-to-azure.md

Author: prmerger-automator[bot]

articles/azure-video-indexer/connect-to-azure.md

@@ -70,10 +70,6 @@ If your storage account is behind a firewall, see [storage account that is behin
 
     :::image type="content" alt-text="Screenshot that shows how to use the classic API." source="./media/create-account/enable-classic-api.png":::
 
-    When creating a storage account for your Media Services account, select **StorageV2** for account kind and **Geo-redundant** (GRS) for replication fields.
-
-    :::image type="content" alt-text="Screenshot that shows how to specify a storage account." source="./media/create-account/create-new-ams-account.png":::
-
     > [!NOTE]
     > Make sure to write down the Media Services resource and account names. 
 1. Before you can play your videos in the Azure Video Indexer web app, you must start the default **Streaming Endpoint** of the new Media Services account.
@@ -101,9 +97,6 @@ The following Azure Media Services related considerations apply:
 * If you plan to connect to an existing Media Services account, make sure the Media Services account was created with the classic APIs.
 
     ![Media Services classic API](./media/create-account/enable-classic-api.png)
-* If you connect to an existing Media Services account, Azure Video Indexer doesn't change the existing media **Reserved Units** configuration.
-
-   You might need to adjust the type and number of Media Reserved Units according to your planned load. Keep in mind that if your load is high and you don't have enough units or speed, videos processing can result in timeout failures.
 * If you connect to a new Media Services account, Azure Video Indexer automatically starts the default **Streaming Endpoint** in it:
 
     ![Media Services streaming endpoint](./media/create-account/ams-streaming-endpoint.png)
@@ -173,10 +166,10 @@ To create a paid account in Azure Government, follow the instructions in [Create
 
 ### Limitations of Azure Video Indexer on Azure Government
 
-*	No manual content moderation available in Government cloud.
+* Only paid accounts (ARM or classic) are available on Azure Government. 
+* No manual content moderation available in Government cloud.
 
     In the public cloud when content is deemed offensive based on a content moderation, the customer can ask for a human to look at that content and potentially revert that decision.
-*	No trial accounts.
 * Bing description - in Gov cloud we won't present a description of celebrities and named entities identified. This is a UI capability only.
 
 ## Clean up resources