Microsoft Power Automate RPA Developer (PL-500) 2025 – 400 Free Practice Questions to Pass the Exam

To hide certain actions in a custom connector from users, selecting them as internal is the appropriate approach. When actions are marked as internal, they become inaccessible to users and are not visible in the user interface. This is particularly useful in scenarios where you may want to keep certain functionalities restricted for administration or integration purposes, ensuring that only a select group can use them. By categorizing actions as internal, you maintain a streamlined experience for end users, allowing them to engage only with the actions that are intended for their use.

The other options do not effectively hide actions from users the way marking them as internal does. Adding words like (HIDDEN) to the action names does not provide any real restriction; users could still see the actions even if they are not intended for them. Disabling access through security roles might limit who can perform actions but does not eliminate visibility to those actions. Finally, sharing only selected actions does not hide others; it merely restricts access in a sharing sense rather than altering the visibility of the actions themselves.