Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Note
This preview capability is subject to the Supplemental Terms of Use for Microsoft Azure Previews.
After you create an automation project, you need a way to package related workflows, connections, parameters, analytics, and settings so they deploy and scale together. Without this boundary, automations for different business processes can get disorganized, making them harder to independently test, monitor, and update.
In Logic Apps Automation, an application provides this deployable and scalable package. You create one application per logical workload or related workflows, for example, order-processing or daily-reports, so each group of related automations stays self-contained inside your project.
This quickstart shows how to create an application in an existing automation project.
For more information, see:
Prerequisites
A Microsoft work or school account that can access the Logic Apps Automation portal.
Your work or school account needs to exist in the same Microsoft Entra tenant as the project creator-owner so they can add you to the project and assign the necessary permissions. If you don't have access, work with the project creator or owner to get access and permissions.
For more information about Microsoft Entra tenants, see Tenant configurations.
The project where you want to create your application.
You need the Contributor or Author role to create applications and workflows.
Note
The project Reader role doesn't have enough permissions to create applications.
Create your application
To create a deployable package for your applications and their components, follow these steps:
Go to the Logic Apps Automation portal, and sign in with your Microsoft work or school account.
From the Projects tab, select the project where you want to create your application.
After the Apps page opens, select Create app.
In the Create application box, for Application name, enter a descriptive name for your application, and then select Create.
Note
Creating an application might take a minute or two. Monitor the Status column, and wait until the application is ready before you create any connections, workflows, or other components.
The Apps page shows your application after the portal finishes.
Continue to the steps for creating a dynamic automation workflow.
Application ownership and privacy
By default, when you create an application, you automatically become the application owner.
As the application owner, you have Contributor role permissions at the application level.
By default, applications are always private. Only the creators (owners) can view and access their applications' contents.
Project owners and contributors can view application metadata for governance. However, they can't view workflow content, connections, or workflow run history.
Other project members can't view the application unless the application creator-owner adds them to the application and gives them the appropriate permissions.
Applications often contain automations that connect to personal accounts. The default privacy model keeps sensitive data obscured and invisible to others unless the application creator-owner chooses otherwise.
Add application members
By default, only the application creator-owner or contributor can access an application and its contents. Before other project members can work on your application, add them as application members by following these steps:
In the Logic Apps Automation portal, on the Projects page, select the project that contains the application you want.
On the Applications page, select the application.
On the application sidebar, select Settings.
On the Settings page, select the User permissions tab, and complete the following steps:
In the Users section, select Add user.
On the Add role assignment pane, in the Select user box, enter the email address for the person you want to add.
The Select user list shows only people in the same Microsoft Entra tenant as you.
From the results, select the correctly matching person.
After the Role section appears, select the role the person needs, based on the principle of least privilege, and then select Add.
The following table describes the available roles at the application level, what they can do, and what they can't do:
Role Can Can't Reader (view only) - View workflows, connections, and parameters.
- View workflow run history.- Create, edit, or delete anything.
- Trigger or cancel workflow runs.Contributor - View and edit workflows, connections, and parameters.
- View workflow run history.
- Trigger, cancel, and resubmit workflow runs.
- Manage application permissions.Delete the application. (owner only) Note
By design, the Author role is unavailable at the application level.
Troubleshoot problems
The following table describes some common problems that you might encounter and ways to resolve them:
| Problem | Cause | Resolution |
|---|---|---|
| "I can't create an application." | You have the project Reader role. | Ask a project Contributor to upgrade you to project Author or Contributor. |
| "I can't view any applications in the project." | By default, applications are private and invisible to others except the application creator-owner. | Ask the application owner to add you to the application, or make you a project Contributor, if you only need to view the application metadata for governance. |
| "I can't manage permissions on applications." | You need the application Contributor role. | Ask the application owner or a Contributor to make you an application Contributor. |
| "An application lost its owner." | When an application owner leaves your Microsoft Entra tenant, you get the following results: - Existing members keep their access. - Only the Project Owner can delete the application. - The application still appears in the project's governance view. |
|
| "I can't delete applications." | Only the application owner can delete their application. | Contact the application owner. If the owner is unavailable, and the application is orphaned, the project owner can delete orphaned applications. |