Skip to content

Commit c525fe3

Browse files
committed
Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into amrmon
2 parents 15bb880 + ecbb042 commit c525fe3

7 files changed

Lines changed: 76 additions & 39 deletions

File tree

articles/active-directory-b2c/customize-ui-with-html.md

Lines changed: 29 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: kengaderdus
66
manager: CelesteDG
77
ms.service: azure-active-directory
88
ms.topic: how-to
9-
ms.date: 02/17/2025
9+
ms.date: 03/04/2026
1010
ms.author: kengaderdus
1111
ms.subservice: b2c
1212
zone_pivot_groups: b2c-policy-type
@@ -440,6 +440,34 @@ To use the sample:
440440
1. Now modify the policy, pointing to your HTML file, as mentioned previously.
441441
1. If you see missing fonts, images, or CSS, check your references in the extensions policy and the `\*.html` files.
442442

443+
444+
### Bootstrap dependency in sample templates
445+
446+
The [sample templates](https://github.com/azure-ad-b2c/html-templates) use **Bootstrap 3.3.5**, sourced from the official Bootstrap CDN. This version has been validated and tested with Azure AD B2C.
447+
448+
The templates reference the following CDN URL for Bootstrap CSS:
449+
450+
```
451+
https://cdn.jsdelivr.net/npm/bootstrap@3.3.5/dist/css/bootstrap.min.css
452+
```
453+
454+
The default configuration in the template HTML files includes a link element similar to the following example:
455+
456+
```xml
457+
<link href="https://cdn.jsdelivr.net/npm/bootstrap@3.3.5/dist/css/bootstrap.min.css" rel="stylesheet" type="text/css" />
458+
```
459+
460+
For the official Bootstrap 3.3.5 download and CDN details, see [Bootstrap 3.3 Getting Started](https://getbootstrap.com/docs/3.3/getting-started/#download-cdn).
461+
462+
#### Replace the CDN reference
463+
464+
You can replace the CDN reference with your organization's internal CDN or a locally hosted copy to meet reliability, security, or compliance requirements.
465+
466+
> [!IMPORTANT]
467+
> The templates are validated specifically against Bootstrap 3.3.5. Upgrading, downgrading, or otherwise modifying the Bootstrap version might introduce styling, layout, or component compatibility issues.
468+
469+
If you change the Bootstrap version, you're responsible for completing regression testing to validate that your customized templates work correctly with Azure AD B2C. Retain the validated version unless you've completed appropriate testing.
470+
443471
## Use company branding assets in custom HTML
444472

445473
To use [company branding](customize-ui.md#configure-company-branding) assets in a custom HTML, add the following tags outside the `<div id="api">` tag. The image source is replaced with that of the background image and banner logo.

articles/application-gateway/for-containers/web-application-firewall.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -136,7 +136,7 @@ spec:
136136
The following functionality is not supported on an Azure Web Application Firewall policy that's associated with Application Gateway for Containers:
137137

138138
- **Cross-region, cross-subscription policy**: Your WAF policy must be in the same subscription and region as your Application Gateway for Containers resource.
139-
- **Core Rule Set (CRS) managed rules**: An Application Gateway for Containers WAF supports only Default Rule Set (DRS) managed rule sets.
139+
- **Core Rule Set (CRS) managed rules**: An Application Gateway for Containers WAF supports only Default Rule Set (DRS) 2.1 managed rule set.
140140
- **Legacy Bot Manager Rule Set**: Bot Manager Ruleset 0.1 isn't supported, but Bot Manager Ruleset versions 1.0 and 1.1 are supported.
141141
- **JavaScript challenge actions on Bot Manager rules**: You can't set the action on a Bot Manager rule to JavaScript challenge.
142142
- **Captcha challenge actions on Bot Manager rules**: You can't set the action on a Bot Manager rule to Captcha.

articles/cost-management-billing/manage/supported-payment-methods.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ For more information about payment methods, see [Add, update, or remove a paymen
3434
| Argentina || | ||| | | |
3535
| Armenia || | ||| | | |
3636
| Australia || | ||| | | |
37-
| Austria || | ||| | | |
37+
| Austria || | ||| | | |
3838
| Azerbaijan || | ||| | | |
3939
| Bahamas || | ||| | | |
4040
| Bahrain || | ||| | | |
@@ -76,7 +76,7 @@ For more information about payment methods, see [Add, update, or remove a paymen
7676
| Finland || | ||| | | |
7777
| France || | ||| | | |
7878
| Georgia || | ||| | | |
79-
| Germany || | ||| | | |
79+
| Germany || | ||| | | |
8080
| Ghana || | ||| | | |
8181
| Greece || | ||| | | |
8282
| Guatemala || | ||| | | |
@@ -116,7 +116,7 @@ For more information about payment methods, see [Add, update, or remove a paymen
116116
| Morocco || | ||| | | |
117117
| Namibia || | ||| | | |
118118
| Nepal | | | ||| | | |
119-
| Netherlands || | ||| | | |
119+
| Netherlands || | ||| | | |
120120
| New Zealand || | ||| | | |
121121
| Nicaragua || | ||| | | |
122122
| Nigeria || | ||| | | |

articles/network-watcher/vnet-flow-logs-overview.md

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -64,6 +64,18 @@ In addition to existing support to identify traffic that [network security group
6464
>
6565
> If you enable network security group flow logs on the network security group of a subnet, then you enable virtual network flow logs on the same subnet or parent virtual network, you might get duplicate logging or only virtual network flow logs.
6666
67+
## Platform Rules
68+
69+
#### What is a platform rule in flow logs
70+
71+
In flow logs, a platform rule represents network traffic that is processed by the Azure platform itself rather than by user‑configured rules, such as Network Security Groups (NSGs) or Azure Virtual Network Manager rules. This traffic is handled automatically by the platform and is not the result of an explicit allow or deny rule defined within a deployment. Platform rule entries provide visibility into system‑managed or infrastructure‑level traffic. If analysis is focused only on traffic evaluated by explicitly configured rules, these entries can be filtered out during log analysis.
72+
73+
In some scenarios, traffic associated with you application or workload may appear under a platform rule. This can occur in a limited number of well‑understood cases, such as when load‑balanced connections are recreated as part of normal platform operations, or when return traffic does not require rule evaluation for the response path. In these cases, the traffic is processed as expected, but the flow log may associate it with a platform rule instead of a user‑defined rule.
74+
75+
#### Does the presence of platform rules affect traffic?
76+
77+
No. Platform rules do not change your traffic behavior, connectivity, security posture, or performance. They only affect how certain network flows are represented in flow logs. Platform rule entries are provided for informational purposes. Excluding them from analysis does not impact how traffic is handled. If traffic appears under a platform rule and does not align with the scenarios described above, the behavior can be investigated further. In such cases, reaching out through Azure support channels is recommended so the flow logs can be reviewed in detail.
78+
6779
## How logging works
6880

6981
Key properties of virtual network flow logs include:

0 commit comments

Comments
 (0)