Merge pull request #8917 from simonxjx/simon-3

Fix the issue of file name too long

Author: Simonx Xu

support/power-platform/dataverse/email-exchange-synchronization/incoming-emails-unexpectedly-synchronized-have-unexpected-missing-data.md

@@ -63,7 +63,7 @@ To avoid duplicate emails to be tracked or synchronized:
 2. Navigate to **Settings** > **Email Configuration** > **Email Configuration Settings**.
 3. Under the **Set tracking options for emails between Microsoft Dynamics 365 users** setting, clear the **Track emails sent between Dynamics 365 users as two activities** option.
 
-   :::image type="content" source="media/incoming-emails-unexpectedly-synchronized-have-unexpected-missing-data/track-emails-sent-between-dynamics-365-as-two-activities.png" alt-text="Screenshot that shows the Set tracking options for emails between Microsoft Dynamics 365 users setting.":::
+   :::image type="content" source="media/incoming-emails-unexpectedly-synchronized-have-unexpected-missing-data/track-emails-sent.png" alt-text="Screenshot that shows the Set tracking options for emails between Microsoft Dynamics 365 users setting.":::
 
 For more information about how the system detects if an email should be automatically promoted, see [Specify which emails are automatically tracked](/power-platform/admin/email-message-filtering-correlation).
 

…tween-dynamics-365-as-two-activities.png …ected-missing-data/track-emails-sent.pngsupport/power-platform/dataverse/email-exchange-synchronization/media/incoming-emails-unexpectedly-synchronized-have-unexpected-missing-data/track-emails-sent-between-dynamics-365-as-two-activities.png renamed to support/power-platform/dataverse/email-exchange-synchronization/media/incoming-emails-unexpectedly-synchronized-have-unexpected-missing-data/track-emails-sent.png support/power-platform/dataverse/email-exchange-synchronization/media/incoming-emails-unexpectedly-synchronized-have-unexpected-missing-data/track-emails-sent-between-dynamics-365-as-two-activities.png renamed to support/power-platform/dataverse/email-exchange-synchronization/media/incoming-emails-unexpectedly-synchronized-have-unexpected-missing-data/track-emails-sent.png

@@ -25,7 +25,7 @@ Consider either of the following scenarios:
 - You install a new Windows Server 2016 Certification Authority (CA).
 - You configure the compatibility settings of a certificate template by setting **Certification Authority** to **Windows Server 2016** and **Certificate recipient** to **Windows 10 / Windows Server 2016**.
 
-    :::image type="content" source="media/cannot-select-windows-server-2016-ca-compatible-certificate-templates/compatibility-settings-of-a-certificate-template.png" alt-text="Screenshot of the compatibility settings of a certificate template, showing the compatibility level set to Windows Server 2016 and Windows 10.":::
+    :::image type="content" source="media/cannot-select-windows-server-2016-ca-compatible-certificate-templates/compatibility-settings-certificate-template.png" alt-text="Screenshot of the compatibility settings of a certificate template, showing the compatibility level set to Windows Server 2016 and Windows 10.":::
 
 When Windows 10 users try to request certificates by using the CA Web enrollment page (the CEP URL), the certificate template that you configured as described here is not listed as an available template.
 
@@ -44,7 +44,7 @@ To work around this issue, follow these steps:
    - **Certificate Authority**: **Windows Server 2012 R2**  
    - **Certificate recipient**: **Windows 8.1 / Windows Server 2012 R2**  
 
-        :::image type="content" source="media/cannot-select-windows-server-2016-ca-compatible-certificate-templates/compatibility-settings-certificate-template-authority-recipient.png" alt-text="Screenshot of the compatibility settings of a certificate template, showing the compatibility level set to Windows Server 2012 R2 and Windows 8.1.":::
+        :::image type="content" source="media/cannot-select-windows-server-2016-ca-compatible-certificate-templates/certificate-template-authority-recipient.png" alt-text="Screenshot of the compatibility settings of a certificate template, showing the compatibility level set to Windows Server 2012 R2 and Windows 8.1.":::
 
 2. Wait 30 minutes for the CEP server to receive the updated template information (or use the IISReset tool to restart the server).
 3. On the client computer, clear the client-side Enrollment Policy Cache by using the following command in a Command Prompt window:

support/windows-server/certificates-and-public-key-infrastructure-pki/cannot-select-windows-server-2016-ca-compatible-certificate-templates.md

@@ -70,7 +70,7 @@ To configure the IIS Web server in the resource forest, follow these steps:
 
 2. On the IIS Web server, enable **Active Directory Client Certificate Authentication**.
 
-    :::image type="content" source="./media/set-up-certificate-based-authentication-across-forest-without-trust/enable-active-directory-client-certificate-authentication.png" alt-text="Enabling the Active Directory Client Certificate Authentication.":::
+    :::image type="content" source="./media/set-up-certificate-based-authentication-across-forest-without-trust/enable-client-certificate-authentication.png" alt-text="Enabling the Active Directory Client Certificate Authentication.":::
 
 3. On your website, configure **SSL Settings** to **Require SSL** and then under **Client certificates**, select **Require**.