Skip to content

Commit 0b4f795

Browse files
Merge pull request #292714 from Hacks4Snacks/graymark/nexuspolicyupdate
[operator-nexus] Include note regarding Azure Policy and managed resources
2 parents 7b7bc73 + b6e01b1 commit 0b4f795

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

articles/operator-nexus/howto-use-azure-policy.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -57,6 +57,9 @@ If you're new to Azure Policy, here are some helpful resources that you can use
5757
> * Review your organization's security and compliance requirements.
5858
> * Identify specific Azure Policy features relevant to your needs.
5959
60+
> [!NOTE]
61+
> Operator Nexus managed infrastructure resources may not align with custom internal policies based on the management and release patterns of the platform. Additionally, Azure baseline policies where input is required (e.g., list of authorized ports) or installed extension expectations (e.g., Azure Kubernetes Service clusters should have the Azure Policy add-on for Kubernetes installed) will fail by default. Nexus managed resources such as the Cluster Manager are not intended for direct customer interaction nor support customer deployed extensions or integrations.
62+
6063
## Use Azure Policy to secure your Nexus BMM resources
6164

6265
The Operator Nexus service offers a built-in policy definition that is recommended to assign to your Nexus BMM resources. This policy definition is called **[Preview]: Nexus compute machines should meet security baseline**. This policy definition is used to ensure that your Nexus BMM resources are configured with industry best practice security settings.

0 commit comments

Comments
 (0)