EPM elevation rules

Dates from the page's own change log or history section. They describe earlier edits, not upcoming policy.

• Creating elevation rules with Endpoint Privilege ManagementRequirement1 condition
• Creating elevation rules with Endpoint Privilege ManagementRequirement1 condition
• Creating elevation rules with Endpoint Privilege ManagementRequirement
• About elevation rules policyRequirementScopeRecommendation2 conditions
• About elevation rules policyRequirement
• About elevation rules policyRequirementException6 conditions
• About elevation rules policyRequirementScope3 conditions
• About elevation rules policyExceptionRecommendation1 condition
• Defining rules for use with Endpoint Privilege ManagementExceptionRecommendation2 conditions
• File hash rulesRecommendation
• Certificate rulesRecommendation
• Certificate rulesExceptionRecommendation1 condition
• Rules containing file nameScope
• Deploying rules created with Endpoint Privilege ManagementException3 conditions
• Deploying rules created with Endpoint Privilege ManagementException2 conditions
• Create elevation rules policyException2 conditions
• Create elevation rules policyRequirement2 conditions
• Create elevation rules policyRequirement
• Create elevation rules policyRequirementScope3 conditions
• Create elevation rules policyRequirementScope1 condition
• Create elevation rules policyRecommendation
• Automatically configure elevation rules for Windows elevation rules policyScopeRecommendation4 conditions
• Manually configure elevation rules for Windows elevation rules policyRecommendation
• Manually configure elevation rules for Windows elevation rules policyRequirementExceptionScopeRecommendation20 conditions
• Use variables in elevation rulesException2 conditions
• Use file arguments for elevation rulesRequirementException2 conditions
• Use file arguments for elevation rulesRequirementException2 conditions
• Reusable settings groupsRequirementException1 condition
• Reusable settings groupsRecommendation

Captured 6 Oct 17:57 UTC; extracted 16 Oct 16:10 UTC. Extractor: microsoft-1/9/fc65ebeb286710c0a830833db8a7e5de7e266b79981fe9c7c34479be9369ad3c/legacy.

Earlier unavailable versions and edits between checks are unknown. A missing statement requires review; it does not mean the policy was cancelled. Recovered historical statements are not original revision snapshots.

Compact evidence remains available after full document bodies expire. Earlier extractions can have different vocabulary or capture limitations.

• 19 Oct 01:09 UTC · 64 candidates
• 12 Oct 19:50 UTC · 63 candidates
• 6 Oct 17:57 UTC · 45 candidates
• 5 Oct 17:50 UTC · 45 candidates