Skip to content

Commit b4dcd60

Browse files
authored
Update troubleshoot-domain-ssl-certificates.md
Fix list format issue
1 parent 3902777 commit b4dcd60

File tree

1 file changed

+8
-12
lines changed

1 file changed

+8
-12
lines changed

articles/app-service/troubleshoot-domain-ssl-certificates.md

Lines changed: 8 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -118,13 +118,11 @@ The Key Vault used to store the App Service Certificate is missing access policy
118118

119119
To modify the access polices for the key vault, follow these steps:
120120

121-
<ol>
122-
<li>Sign in to the Azure portal. Select the Key Vault used by your App Service Certificate. Navigate to Access policies.</li>
123-
<li>If you do not see the two Service Principals listed you will need to add them. If they are available, verify the permissions include the recommended secret and certificate permissions.</li>
124-
<li>Add a Service Principal by selecting "Create". Then select the needed permissions for Secret and Certificate permissions.</li>
125-
<li>For the Principal, enter the value(s) given above in the search box. Then select the principal.</li>
126-
</ol>
127-
121+
1. Sign in to the Azure portal. Select the Key Vault used by your App Service Certificate. Navigate to Access policies.</li>
122+
2. If you do not see the two Service Principals listed you will need to add them. If they are available, verify the permissions include the recommended secret and certificate permissions.</li>
123+
3. Add a Service Principal by selecting "Create". Then select the needed permissions for Secret and Certificate permissions.</li>
124+
4. For the Principal, enter the value(s) given above in the search box. Then select the principal.</li>
125+
128126
#### Cause 2: The app service has not yet synced with the new certificate
129127

130128
The App Service automatically syncs your certificate within 48 hours. When you rotate or update a certificate, sometimes the application is still retrieving the old certificate and not the newly updated certificate. The reason is that the job to sync the certificate resource hasn't run yet. To resolve this problem, sync the certificate manually, which automatically updates the hostname bindings for the certificate in App Service without causing any downtime to your apps.
@@ -133,11 +131,9 @@ The App Service automatically syncs your certificate within 48 hours. When you r
133131

134132
To force a sync for the certificate, follow these steps:
135133

136-
<ol>
137-
<li>Sign in to the [Azure portal](https://portal.azure.com). Select **App Service Certificates**, and then select the certificate.</li>
138-
<li>Select **Rekey and Sync**, and then select **Sync**. The sync takes some time to finish.</li>
139-
<li>When the sync completes, the following notification appears: "Successfully updated all the resources with the latest certificate."</li>
140-
</ol>
134+
1. Sign in to the [Azure portal](https://portal.azure.com). Select **App Service Certificates**, and then select the certificate.</li>
135+
2. Select **Rekey and Sync**, and then select **Sync**. The sync takes some time to finish.</li>
136+
3. When the sync completes, the following notification appears: "Successfully updated all the resources with the latest certificate."</li>
141137

142138
### An App Service is showing the wrong certificate
143139

0 commit comments

Comments
 (0)