Address Policy Complexities

Enforcement results are impacted by factors including:

• Rule type and rank:

  • Absolute vs Default policies

  • The catch-all setting for the workspace

  See Policy Rank: Absolute, Default, and Catch-All.

• Order of policies within the workspace

  See Policy Priorities.

• Policies inherited from parent or ancestor scopes, including the catch-all rule

  You will want to ensure that a higher-priority policy is not hitting traffic before the policy that you expect to hit that traffic.

  To see the impact of policies in ancestor scopes, run live policy analysis on all involved scopes. See Live Policy Analysis.

  When you are ready to enforce the policies in a workspace, a wizard shows you which inherited policies impact workloads in the workspace. For information, see Policy Enforcement Wizard.

• Cross-scope policy interactions

  (When consumer and provider are in different scopes, or one end of the conversation is in a different scope than the policy)

  See When Consumer and Provider Are in Different Scopes: Policy Options.

• Situations in which the actual consumer or provider in a policy may differ from the default configured consumer and provider, for example in failover scenarios.

  See Effective Consumer or Effective Provider.