First Step to Deploy an Auto-Labeling Policy for Encrypted Emails?

Why the Answer Is Correct

Microsoft Purview auto-labeling policies are deployed through a controlled workflow: after you define the sensitive info type and locations, the policy first runs in simulation mode so that matching emails are identified without applying the encryption label. Simulation mode lets you review what would be encrypted, adjust the rule if needed, and then turn the policy on or let it auto-enable after seven days. Because the question asks what to do first to deploy the policy, running it in simulation mode (A) is the correct action. Community voters and commenters, including Ody and Khanbaba43, consistently select A for this reason.

Why the Other Options Are Wrong

Option B is unrelated: turning on co-authoring for files with sensitivity labels affects file collaboration and does not deploy an email auto-labeling policy. Option C is a monitoring step; Activity explorer can show label activity, but it is not the required first action to deploy the policy, and it does not validate the new auto-labeling rule before enforcement. Option D is the later stage: turning on the policy enforces encryption immediately, so doing that first skips the simulation and review step that Microsoft's auto-labeling workflow expects.

Community Comment Notes

Ody explained that "The only options are Simulation Mode and Off" and noted that simulation mode includes an option to default the policy to on after seven days, which matches the Microsoft Purview deployment model. Murad01 called this a repeated question and said the "Given answer is correct", reinforcing that the source key aligns with product behavior. Khanbaba43 also wrote "Repeated question. Answer: A", and the unanimous A votes reflect the same consensus without contradicting the official workflow.