A company uses Dynamics 365 Customer Service. Managers state that support representatives can view contact social security numbers when the representatives open contact records. Support representatives must only be able to verify that the social security number is saved. They must not be able to view the number. You need to configure the application to resolve the issue. What should you do?

Field-level security is the designated feature in Dynamics 365 and Microsoft Dataverse for restricting access to specific, high-impact fields. By enabling field-level security on the social security number column, you can create a field security profile for support representatives that denies them 'Read' permission for that specific column. When a user without read permission views a record, the system will display the column but mask the data with asterisks (e.g., ''). This allows representatives to verify that a number is present without viewing the sensitive information, directly fulfilling the requirement.

A. Create a Power Automate flow. Power Automate is a workflow automation tool, not a real-time security enforcement mechanism for user interface elements. It is unsuitable for controlling field visibility or masking data on a form.
B. Set up a business rule to hide the column if it contains data. A business rule can hide a column, but this would prevent representatives from verifying if the number is saved. Business rules cannot mask data; they can only control visibility or set values.
D. Remove the column from the form. Removing the column from the form would prevent all users, including authorized ones, from seeing it. It also fails the requirement for representatives to verify that the number is saved.

1. Microsoft Dataverse Documentation

"Field-level security": "You can set field-level security to restrict access to specific high business impact fields in an entity to only specified users or teams... When a user tries to access a secured field

the system checks the user's privileges for that specific field... If the user does not have Read permission for the field

they will see instead of the actual data."

Source: Microsoft Learn

dataverse/field-level-security.

2. Microsoft Dataverse Documentation

"Create a business rule or business recommendation": This document outlines the actions available for business rules

which include setting field values

visibility

and requirement levels

but not data masking.

Source: Microsoft Learn

dataverse/create-business-rules-recommendations-apply-logic-form.

3. Microsoft Power Platform Documentation

"Overview of cloud flows": This source describes Power Automate cloud flows as a tool for automating tasks and processes

confirming it is not intended for real-time

on-form security control.

Source: Microsoft Learn

power-automate/overview-cloud.