Update screenshots in the images/azure directory (#34520)

Co-authored-by: github-actions <github-actions@github.com>
Co-authored-by: Ben Ahmady <32935794+subatoi@users.noreply.github.com>

content/admin/configuration/configuring-your-enterprise/deploying-github-ae.md

@@ -32,7 +32,6 @@ The {% data variables.actions.azure_portal %} allows you to deploy the {% data v
    - [Deploy {% data variables.product.product_name %} to Azure Government](https://aka.ms/create-github-ae-instance-gov)
 1. To begin the process of adding a new {% data variables.product.product_name %} account, click **Create GitHub AE account**.
 1. Complete the "Project details" and "Instance details" fields.
-    ![{% data variables.actions.azure_portal %} search result](/assets/images/azure/github-ae-azure-portal-form.png)
     - **Account name:** The hostname for your enterprise
     - **Administrator username:** A username for the initial enterprise owner that will be created in {% data variables.product.product_name %}
     - **Administrator email:** The email address that will receive the login information
@@ -53,7 +52,6 @@ You can use the {% data variables.actions.azure_portal %} to navigate to your {%
 
 1. On the {% data variables.actions.azure_portal %}, in the left panel, click **All resources**.
 1. From the available filters, click **All types**, then deselect **Select all** and select **GitHub AE**:
-    ![{% data variables.actions.azure_portal %} search result](/assets/images/azure/github-ae-azure-portal-type-filter.png)
 
 ## Next steps
 

content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-azure-blob-storage.md

@@ -55,10 +55,10 @@ To configure {% data variables.product.prodname_ghe_server %} to use OIDC with a
 1. Register a new application in Azure Active Directory. For more information, see [Register an application](https://learn.microsoft.com/en-us/azure/active-directory/develop/quickstart-register-app#register-an-application) in the Azure documentation.
 1. In your Azure application, under "Essentials", take note of the values for "Application (client) ID" and "Directory (tenant) ID". These values are used later.
 
-   ![Azure portal showing the Active Directory app "Essentials" section](/assets/images/azure/azure-aad-app-storage-ids.png)
+   ![Screenshot of the "Overview" page in Azure. The first four items in the "Essentials" section are highlighted with an orange outline.](/assets/images/azure/azure-aad-app-storage-ids.png)
 1. In your Azure application, under "Manage", click **Certificates & secrets**, select the **Federated credentials** tab, then click **Add credential**.
 
-   ![Azure portal showing the Active Directory app "certificates & secrets" page](/assets/images/azure/azure-federated-credential.png)
+   ![Screenshot of the "Federated credentials" page in Azure. The "Certificates & secrets" tab, the "Federated credentials" tab, and the "Add credential" button are highlighted with orange outlines.](/assets/images/azure/azure-federated-credential.png)
 1. Enter the following details for the credential:
    1. For "Federated credential scenario", select **Other issuer**.
    1. For "Issuer", enter `https://HOSTNAME/_services/token`, where `HOSTNAME` is the public hostname for {% data variables.location.product_location_enterprise %}. For example, `https://my-ghes-host.example.com/_services/token`.

content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise.md

@@ -160,19 +160,11 @@ To configure the stream in {% data variables.product.prodname_dotcom %} you need
 
 **On Microsoft Azure portal**:
 1. On the Home page, click **Storage Accounts**.
-2. Click the name of the storage account you want to use, then click **Containers**.
-   
-   ![The Containers link in Azure](/assets/images/azure/azure-storage-containers.png)
-
+1. Under "Name", click the name of the storage account you want to use.
+1. Under "Data storage", click **Containers**.
 1. Click the name of the container you want to use.
-1. Click **Shared access tokens**. 
-   
-   ![The shared access token link in Azure](/assets/images/azure/azure-storage-shared-access-tokens.png)
-
-1. In the **Permissions** drop-down menu, change the permissions to only allow `Create` and `Write`.
-   
-   ![The permissions drop-down menu](/assets/images/azure/azure-storage-permissions.png)
-
+1. In the left sidebar, under "Settings", click **Shared access tokens**.
+1. Select the **Permissions** dropdown menu, then select `Create` and `Write` and deselect all other options.
 1. Set an expiry date that complies with your secret rotation policy.
 1. Click **Generate SAS token and URL**.
 1. Copy the value of the **Blob SAS URL** field that's displayed. You will use this URL in {% data variables.product.prodname_dotcom %}.
@@ -200,10 +192,7 @@ Before setting up a stream in {% data variables.product.prodname_dotcom %}, you
 You need two pieces of information about your event hub: its instance name and the connection string.
 
 **On Microsoft Azure portal**:
-1. Search for "Event Hubs".
-
-   ![The Azure portal search box](/assets/images/azure/azure-resources-search.png )
-
+1. At the top of the page, next to "Microsoft Azure", use the search box to search for "Event Hubs".
 1. Select **Event Hubs**. The names of your event hubs are listed.
 
    ![A list of event hubs](/assets/images/help/enterprises/azure-event-hubs-list.png)