How Do You Define an Information Barrier Segment in Microsoft Purview?
You have a Microsoft 365 E5 subscription. You plan to implement information barriers (IBs). You need to create an IB segment named Segment1. What should you use to define Segment1?
Community Votes
73% of anonymous learners picked answer A. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
Tests whether you know IB segments are defined by attribute-based user group filters in the compliance portal — the trap is assuming a Microsoft 365 group or administrative unit is the object that holds segment membership.
Creating an information barrier segment named Segment1 in Microsoft Purview requires a user group filter, not a Microsoft 365 group, distribution list, or administrative unit. This page confirms why option A is the SC-400 answer and how the compliance portal actually builds segments.
Choosing a Microsoft 365 group (C) because it sounds like the natural container for segment membership; in reality Microsoft 365 groups, distribution lists, and administrative units can only appear as filter criteria, never as the segment definition itself.
Community Discussion (6 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
When you create a segment such as Segment1 under Information barriers > Segments in the Microsoft Purview compliance portal, the wizard immediately asks you to add a user group filter — there is no step where you attach a group object. Segment membership is therefore attribute-driven and dynamic: an expression likeDepartment eq 'Marketing' adds every matching user to the segment, and the filter re-evaluates as user attributes change. This is exactly what option A describes, which is why both the source key and the strong community majority land on it. A segment is not a static list; it is a rule, and the rule is the user group filter.Why the Other Options Are Wrong
Option B (a distribution list group), option C (a Microsoft 365 group), and option D (an administrative unit) are all real directory objects, but none of them is the mechanism Purview asks for when defining a segment. A group or distribution list can be referenced inside the filter criteria, and an administrative unit scopes delegated administration in Microsoft Entra ID rather than information barrier membership, so all three are distractors that mimic the word "group" in the correct answer. Choosing any of them leaves you with no way to express the attribute-based membership that IB policies require before you can define policies between segments.Community Comment Notes
CharlieGolf makes the point succinctly with the note that "segments are defined by attributes" and links the Microsoft Learn procedure for defining segments in the compliance portal. SDiwan describes the live portal flow, recalling that after naming the segment the next screen asks for a "User Group Filter" and that the other answer choices "can be used as criteria", which matches the documentation and confirms A. A few learners, including Domza and sswitzer, picked the Microsoft 365 group option — sswitzer did so on the strength of a chat assistant's answer rather than the vendor doc — while BewiseExams simply observed that "there's no other option" once you have seen the wizard. The configuration-concepts link Domza shared actually supports the filter-based definition, not a group object.Official Reference
Exam Strategy
Memorize the portal order of operations: Information barriers > Segments > name the segment > add a User Group Filter built from user attributes. Any SC-400 answer that names a group object (distribution list, Microsoft 365 group, administrative unit) instead of a filter is a distractor.
Frequently Asked Questions
Why can't a Microsoft 365 group be used to define an IB segment like Segment1?
Segments in the Purview compliance portal are defined by attribute-based user group filters. A Microsoft 365 group or distribution list can only be one of the filter criteria, not the segment definition itself.
Where exactly do you create Segment1 and add its user group filter?
In the Microsoft Purview compliance portal under Information barriers > Segments: name the segment first, then the next screen prompts you to add a User Group Filter such as Department eq 'Marketing'.