A company uses Power Apps. Users must be able to view only the address1 columns in the Account table. You need to ensure other address columns are…

Column-level security (also known as field security) is the appropriate Microsoft Dataverse feature for this requirement. It allows administrators to restrict user access to specific, sensitive columns within a table. By creating a field security profile that denies 'Read' permission for the other address columns and assigning this profile to the relevant users or teams, those columns will be completely hidden from the user interface. This includes forms, reports, and crucially, the column lists available when users create or edit personal views and filters.

A. Disabling the search option for columns only removes them from being indexed for search and from appearing in the Advanced Find search criteria, but it does not prevent users from adding them to views.

B. Business rules operate at the form level to show or hide columns. They do not affect which columns are available to a user when they are creating or editing views or using Advanced Find.

C. Deleting columns is a permanent and destructive action that results in the loss of all data within those columns. This is an irreversible data structure change, not a security or visibility setting.

1. Microsoft Power Platform documentation

"Column-level security to control access." This document states

"You can restrict access to specific high-business-impact columns to specific users and teams... When a user doesn't have Read access to a column

that column won't be displayed in a view

form

or report." This directly supports the use of column-level security to make columns non-visible.

Source: Microsoft Learn

Power Platform / Administer Power Platform / Security and governance / Column-level security to control access.

2. Microsoft Power Apps documentation

"Create a business rule for a table." This document clarifies the scope of business rules: "Business rules you create for a table apply to both canvas and model-driven apps if you set the scope to All Forms... They are not applied for forms in model-driven apps that are not main forms or UCI forms." This confirms that business rules are form-scoped and would not affect view creation.

Source: Microsoft Learn

Power Apps / Maker / Dataverse / Create a business rule for a table.

3. Microsoft Power Apps documentation

"Create and edit columns for Dataverse." The description of the 'Searchable' property confirms its purpose: "This option controls whether the column is included in the columns searched when users use the search for rows feature for the app." This shows it does not control general visibility for view editing.

Source: Microsoft Learn

Power Apps / Maker / Dataverse / Create and edit columns for Dataverse.

4. Microsoft Power Apps documentation

"Delete a column." This section warns

"When you delete a column

any data stored in the column is lost. The only way to recover data from a column that was deleted is to restore the database from a point before the column was deleted." This highlights why deleting columns is inappropriate for a security requirement.

Source: Microsoft Learn

Power Apps / Maker / Dataverse / Create and edit columns for Dataverse using Power Apps portal.