image
Summary
Start course
Difficulty
Beginner
Duration
13m
Students
35
Ratings
5/5
Description

This course starts with an overview of what is meant by defining a policy scope. We then review the shortcomings of static scope definitions and investigate how an adaptive scope solution can solve those problems. Having examined the theory, we will then implement an adaptive scope in the context of a regulatory record data retention policy.

Learning Objectives

  • Gain an overview of adaptive policy scopes
  • Examine adaptive scope use cases
  • Implement an adaptive scope with a record data retention policy

Intended Audience

  • Students who want to learn about adaptive policy scopes, when to use them, and how to create them
  • Students preparing for the SC-400: Microsoft Information Protection Administrator exam

Prerequisites 

  • There are no mandatory prerequisites required to take this course, but knowledge of data loss prevention policies would be beneficial
Transcript

In summary, a static scope is manually defined using locations that can be refined to include or exclude specific named instances, like email addresses within the location or channel. Static scopes tend to be broad and maintenance intensive.

While adaptive scopes use similar locations, Users, SharePoint sites, and Microsoft 365 groups, items are defined as being in-scope based on their properties. By using attributes, items are automatically in scope based on qualifying rules, thus reducing manual maintenance.

Without adaptive policy scopes, organizations may be limited to applying the same DLP policies across the entire organization, regardless of the sensitivity of the data or the level of risk associated with it. This approach can lead to policies that are too broad, leading to unnecessary alerts and disruptions, or too restrictive, causing delays or hindrances to productivity.

My name is Hallam Webber, and we’ve been looking at adaptive policy scopes.

About the Author
Students
21210
Courses
72
Learning Paths
14

Hallam is a software architect with over 20 years experience across a wide range of industries. He began his software career as a  Delphi/Interbase disciple but changed his allegiance to Microsoft with its deep and broad ecosystem. While Hallam has designed and crafted custom software utilizing web, mobile and desktop technologies, good quality reliable data is the key to a successful solution. The challenge of quickly turning data into useful information for digestion by humans and machines has led Hallam to specialize in database design and process automation. Showing customers how leverage new technology to change and improve their business processes is one of the key drivers keeping Hallam coming back to the keyboard.