@@ -161,8 +161,8 @@ With an Azure Firewall, you automatically get the following configured with the
161
161
| definitionupdates.microsoft.com:443 |
162
162
| go.microsoft.com:80 |
163
163
| go.microsoft.com:443 |
164
- | < www.microsoft.com:80 > |
165
- | < www.microsoft.com:443 > |
164
+ | www.microsoft.com:80 |
165
+ | www.microsoft.com:443 |
166
166
| wdcpalt.microsoft.com:443 |
167
167
| wdcp.microsoft.com:443 |
168
168
| ocsp.msocsp.com:443 |
@@ -173,7 +173,7 @@ With an Azure Firewall, you automatically get the following configured with the
173
173
| mscrl.microsoft.com:80 |
174
174
| crl.microsoft.com:443 |
175
175
| crl.microsoft.com:80 |
176
- | < www.thawte.com:443 > |
176
+ | www.thawte.com:443 |
177
177
| crl3.digicert.com:80 |
178
178
| ocsp.digicert.com:80 |
179
179
| ocsp.digicert.com:443 |
@@ -200,7 +200,7 @@ With an Azure Firewall, you automatically get the following configured with the
200
200
| management.core.windows.net:443 |
201
201
| management.core.windows.net:80 |
202
202
| management.azure.com:443 |
203
- | < www.msftconnecttest.com:80 > |
203
+ | www.msftconnecttest.com:80 |
204
204
| shavamanifestcdnprod1.azureedge.net:443 |
205
205
| validation-v2.sls.microsoft.com:443 |
206
206
| flighting.cp.wd.microsoft.com:443 |
@@ -378,9 +378,9 @@ Linux isn't available in US Gov regions and is thus not listed as an optional co
378
378
| v10ortex-win.data.microsoft.com:80 |
379
379
| wp.microsoft.com:80 |
380
380
| dcpalt.microsoft.com:80 |
381
- | < www.microsoft.com:80 > |
382
- | < www.msftconnecttest.com:80 > |
383
- | < www.thawte.com:80 > |
381
+ | www.microsoft.com:80 |
382
+ | www.msftconnecttest.com:80 |
383
+ | www.thawte.com:80 |
384
384
| admin.core.usgovcloudapi.net:443 |
385
385
| azperfmerges.blob.core.windows.net:443 |
386
386
| azperfmerges.blob.core.windows.net:443 |
0 commit comments