Publishing & Sharing

Publishing & Sharing Automation Tasks

Publishing makes an automation task available to authorized users in the Published Tasks experience. You can control the display title, description, and minimum role required to execute the task.

How Publishing Works

In the task configuration view, use the Publish action to open the publish dialog. The dialog captures three values:

• Published Title (required): the name users see

• Published Description (optional): user-facing description

• Minimum Required Role (optional): access control for visibility and execution

If no role is selected, the task is available to all authenticated users in the tenant.

Publish or Un-Publish

Publish

1. Open the task configuration

2. Click Publish

3. Set title, description, and minimum role

4. Confirm publish

Un-Publish

1. Open the same task configuration

2. Click Un-Publish

3. Confirm removal from Published Tasks

Role Access

Published task access is role-aware and follows a minimum-role model.

• None/User: available to authenticated users

• Operator: available to Operators and TenantAdmins

• TenantAdmin: available only to TenantAdmins

Direct Task Access

Publishing is for self-service execution. Direct task access is for sharing a specific automation task with named users or AZExecute tenant groups so they can view, use, edit, or manage that task without receiving broad Operator access.

• Viewer: can see the task and its allowed read-only details

• User: can use the task where execution is allowed

• Editor: can update task configuration

• Owner: can manage access for the task

Users with direct task access open the task from Operations > Automation. If they are not Operators or TenantAdmins, AZExecute only shows the automation-task area and the actions allowed by their task access level.

Group grants use AZExecute tenant groups. This keeps access predictable inside AZExecute and does not require Microsoft Graph groups for task sharing.

What End Users See

Users work from the Published Tasks list where they can:

• Search by published title or description

• Expand task details (steps, parameters, last run)

• Execute tasks they are authorized to run

• Open task-specific execution history from the History action

Operational Notes

• Publishing changes are reflected immediately in the Published Tasks UI

• Updating a published task affects future executions

• Test task changes as Operator before broadening role access

• Use clear parameter labels/descriptions to reduce user input errors