Merge pull request #288443 from johnmarco/jm-aro-sfi-image-fixes

ARO SFI image fixes

Author: Jill Grant

articles/openshift/configure-azure-ad-ui.md

@@ -40,12 +40,8 @@ Provide a name for the application, for example **aro-azuread-auth**, and fill i
 
 Navigate to **Certificates & secrets** and click on **New client secret** and fill in the details. Make note of the key value, as you'll use it in a later stage. You won't be able to retrieve it again.
 
-![Create a secret](media/aro4-ad-clientsecret.png)
-
 Navigate to the **Overview** and make note of the **Application (client) ID** and **Directory (tenant) ID**. You'll need them in a later stage.
 
-![Retrieve Application (client) and Directory (tenant) IDs](media/aro4-ad-ids.png)
-
 ## Configure optional claims
 
 Application developers can use [optional claims](../active-directory/develop/active-directory-optional-claims.md) in their Microsoft Entra applications to specify which claims they want in tokens sent to their application.
@@ -60,8 +56,6 @@ We'll configure OpenShift to use the `email` claim and fall back to `upn` to set
 
 Navigate to **Token configuration** and click on **Add optional claim**. Select **ID** then check the **email** and **upn** claims.
 
-![Screenshot that shows the email and upn claims that were added.](media/aro4-ad-tokens.png)
-
 ## Assign users and groups to the cluster (optional)
 
 Applications registered in a Microsoft Entra tenant are, by default, available to all users of the tenant who authenticate successfully. Microsoft Entra ID allows tenant administrators and developers to restrict an app to a specific set of users or security groups in the tenant.
@@ -105,12 +99,8 @@ Scroll down to select **Add** under **Identity Providers** and select **OpenID C
 
 Fill in the name as **Microsoft Entra ID**, the **Client ID** as the **Application ID** and the **Client Secret**. The **Issuer URL** is formatted as such: `https://login.microsoftonline.com/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/v2.0`. Replace the placeholder with the Tenant ID you retrieved earlier.
 
-![Fill in OAuth details](media/aro4-oauth-idp-1.png)
-
 Scroll down to the **Claims** section and update the **Preferred Username** to use the value from the **upn** claim.
 
-![Fill in claims details](media/aro4-oauth-idp-2.png)
-
 <a name='verify-login-through-azure-active-directory'></a>
 
 ## Verify login through Microsoft Entra ID

articles/openshift/howto-deploy-with-s2i.md

@@ -61,8 +61,6 @@ https://console-openshift-console.apps.wzy5hg7x.eastus.aroapp.io/
 
 Launch the console URL in a browser and login using the `kubeadmin` credentials.
 
-:::image type="content" source="media/login.png" alt-text="Azure Red Hat OpenShift login screen":::
-
 Switch to the *Developer* perspective instead of the *Administrator* perspective in the left-hand side menu and select `demoproject` in the list of projects. You should then be at the *Topology* page for the project.
 
 :::image type="content" source="media/s2i/project-topology.png" alt-text="Azure Red Hat OpenShift project topology":::

articles/openshift/howto-deploy-with-serverless.md

@@ -57,8 +57,6 @@ https://console-openshift-console.apps.wzy5hg7x.eastus.aroapp.io/
 
 Open a web browser and open the console URL. Log in using `kubeadmin` credentials.
 
-:::image type="content" source="media/login.png" alt-text="A screenshot that shows the Azure Red Hat OpenShift log-in screen":::
-
 ## Install the OpenShift Serverless operator
 
 When you're logged into the OpenShift web console, confirm that you're in *Administrator* view. Open the *Operator Hub* and select the **OpenShift Serverless** operator.