Skip to content

Commit af1ec1d

Browse files
Merge pull request #303827 from yutanglin16/patch-16
Minor edits
2 parents a84f647 + edf6926 commit af1ec1d

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/app-service/app-service-managed-certificate-changes-july-2025.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -79,9 +79,9 @@ We recognize that making applications publicly accessible may conflict with cust
7979
- [CLI: Delete certificate](/cli/azure/webapp/config/ssl#az-webapp-config-ssl-delete)
8080

8181
**Temporary mitigation: DigiCert IP allowlisting**
82-
Some customers may choose to allowlist [DigiCert’s domain validation IPs](https://knowledge.digicert.com/alerts/ip-address-domain-validation) as a short-term workaround. This can help buy time to move away from using ASMC for websites that aren’t publicly accessible, especially given the short notice of the change.
82+
Some customers may choose to allowlist [DigiCert’s domain validation IPs](https://knowledge.digicert.com/alerts/ip-address-domain-validation) as a short-term workaround. This may help maintain certificate issuance while transitioning away from using ASMC for websites that aren’t publicly accessible.
8383
> [!NOTE]
84-
> Allowlisting DigiCert's IP isn’t an official or supported long-term solution. Microsoft’s stance remains that **public access is required** to avoid potential service disruptions. Consider the following:
84+
> Allowlisting DigiCert's IP isn’t an official or supported long-term solution. Microsoft’s stance remains that **public access is required** to avoid potential service disruptions. Keep in mind:
8585
>
8686
> - DigiCert manages its own IPs and may change them without notice.
8787
> - Microsoft doesn’t control DigiCert’s infrastructure and can’t guarantee the documentation stay up to date.

0 commit comments

Comments
 (0)