Linux Training in Coimbatore & Best Linux Server Administration Training Institute NUX SOFTWARE SOLUTIONS FREE DEMO CLASSES AVAILABLE Call us 096263 53489
Select a hub from the dropdown to host your project. If you don't have access to a hub yet, select Create a new hub.
If you're creating a new hub, enter a name.
Select your Azure subscription from the Subscription dropdown. Choose a specific Azure subscription for your project for billing, access, or administrative reasons. For example, this grants users and service principals with subscription-level access to your project.
Leave the Resource group as the default to create a new resource group. Alternatively, you can select an existing resource group from the dropdown.
Enter the Location for the hub and then select Next. The location is the region where the hub is hosted. The location of the hub is also the location of the project. Azure AI services availability differs per region. For example, certain models might not be available in certain regions.
Select an existing Azure AI services resource (including Azure OpenAI) from the dropdown or create a new one.
On the Review and finish page, you see the Azure AI services resource name and other settings to review.
Review the project details and then select Create a project. You see progress of resource creation and the project is created when the process is complete.
Once a project is created, you can access the playground, tools, and other assets in the left navigation panel.
On the project Settings page you can find information about the project, such as the project name, description, and the hub that hosts the project. You can also find the project ID, which is used to identify the project via SDK or API.
Name: The name of the project corresponds to the selected project in the left panel.
Hub: The hub that hosts the project.
Location: The location of the hub that hosts the project. For supported locations, see Azure AI Studio regions.
Subscription: The subscription that hosts the hub that hosts the project.
Resource group: The resource group that hosts the hub that hosts the project.
A dev center is the top-level resource for Azure Deployment Environments that contains the collection of development projects. In the dev center, you specify the common configuration for your projects, such as catalogs with application templates, and the types of environments to which development teams can deploy their code.
A platform engineering team typically sets up the dev center, attaches external catalogs to the dev center, creates projects, and provides access to development teams. Development teams then create environments by using environment definitions, connect to individual resources, and deploy applications.
After you complete this quickstart, developers can use the developer portal, the Azure CLI, or the Azure Developer CLI to create environments in the project to deploy their applications.
Azure role-based access control role with permissions to create and manage resources in the subscription, such as Contributor or Owner.
Create a dev center
First, you create a dev center and attach a catalog to it. The catalog contains the application templates, called environment definitions, that development teams can use to create environments. In this quickstart, you attach the Microsoft quick start catalog, which contains sample environment definitions to help you get started.
To create and configure a dev center in Azure Deployment Environments by using the Azure portal:
Search for Azure Deployment Environments, and then select the service in the results.
In Dev centers, select Create.
In Create a dev center, on the Basics tab, select or enter the following information:
Name
Value
Subscription
Select the subscription in which you want to create the dev center.
Resource group
Either use an existing resource group or select Create new and enter a name for the resource group.
Name
Enter a name for the dev center.
Location
Select the location or region where you want to create the dev center.
Attach a quick start catalog
Select the Azure deployment environment definitions checkbox. Clear the Dev box customization tasks checkbox.
Select Review + Create.
On the Review tab, wait for deployment validation, and then select Create.
You can check the progress of the deployment in your Azure portal notifications.
When the creation of the dev center is complete, select Go to resource. Confirm that you see the dev center overview pane.
Configure a managed identity for the dev center
To allow the creation of environments, the dev center requires permissions on the subscription. You can attach an identity to the dev center, and then assign the necessary permissions to that identity. You can attach either a system-assigned managed identity or a user-assigned managed identity. Learn about the two types of identities.
In this quickstart, you configure a system-assigned managed identity for your dev center. You then assign roles to the managed identity to allow the dev center to create environment types in your subscription.
Attach a system-assigned managed identity
To attach a system-assigned managed identity to your dev center:
In your dev center, on the left menu under Settings, select Identity.
Under System assigned, set Status to On, and then select Save.
In the Enable system assigned managed identity dialog, select Yes. It might take a few minutes for the rest of the fields to appear.
Assign roles for the dev center managed identity
The managed identity that represents your dev center requires access to the subscription where you configure the project environment types, and to the catalog.
In your dev center, on left menu under Settings, select Identity.
Under System assigned > Permissions, select Azure role assignments.
To give Contributor access to the subscription, select Add role assignment (Preview), enter or select the following information, and then select Save:
Name
Value
Scope
Subscription
Subscription
Select the subscription in which to use the managed identity.
Role
Contributor
To give User Access Administrator access to the subscription, select Add role assignment (Preview), enter or select the following information, and then select Save:
Name
Value
Scope
Subscription
Subscription
Select the subscription in which to use the managed identity.
Role
User Access Administrator
Create an environment type
Use an environment type to help you define the different types of environments your development teams can deploy. You can apply different settings for each environment type.
In the Azure portal, go to Azure Deployment Environments.
In Dev centers, select your dev center.
In the left menu under Environment configuration, select Environment types, and then select Create.
In Create environment type, enter the following information, and then select Add.
Name
Value
Name
Enter a name for the environment type.
Tags
Optionally, enter a tag name and a tag value.
An environment type that you add to your dev center is available in each project in the dev center, but environment types aren't enabled by default. When you enable an environment type at the project level, the environment type determines the managed identity and subscription that are used to deploy environments.
Create a project
In Azure Deployment Environments, a project represents a team or business function within the organization. For example, you might create a project for the implementation of an e-commerce application, which has a development, staging, and production environment. For another project, you might define a different configuration.
When you associate a project with a dev center, all the settings for the dev center are automatically applied to the project. Each project can be associated with only one dev center.
To create an Azure Deployment Environments project in your dev center:
In the Azure portal, go to Azure Deployment Environments.
In the left menu under Configure, select Projects.
In Projects, select Create.
In Create a project, on the Basics tab, enter or select the following information:
Name
Value
Subscription
Select the subscription in which you want to create the project.
Resource group
Either use an existing resource group or select Create new and enter a name for the resource group.
Dev center
Select a dev center to associate with this project. All settings for the dev center apply to the project.
Name
Enter a name for the project.
Description (Optional)
Enter any project-related details.
On the Review + Create tab, wait for deployment validation, and then select Create.
Confirm that the project was successfully created by checking your Azure portal notifications. Then, select Go to resource. Confirm that you see the project overview pane.
Create a project environment type
In Azure Deployment Environments, project environment types are a subset of the environment types that you configure for the dev center. They help you preconfigure the types of environments that specific development teams can create.
In the left menu under Environment configuration, select Environment types, and then select Add.
In Add environment type to <project-name>, enter or select the following information:
Name
Value
Type
Select a dev center level environment type to enable for the specific project.
Deployment subscription
Select the subscription in which the environment is created.
Deployment identity
Select either a system-assigned identity or a user-assigned managed identity to perform deployments on behalf of the user.
Permissions on environment resources > Environment creator role(s)
Select the roles to give access to the creator of the environment resources.
Permissions on environment resources > Additional access
Select the users or Microsoft Entra groups to assign to specific roles on the environment resources.
Tags
Enter a tag name and a tag value. These tags are applied on all resources that are created as part of the environment.
Give access to the development team
Before developers can create environments based on the environment types in a project, you must provide access for them through a role assignment at the level of the project. The Deployment Environments User role enables users to create, manage, and delete their own environments. You must have sufficient permissions to a project before you can add users to it.
