Muokkaa

Jaa


How to create and manage an Azure AI Studio hub

In AI Studio, hubs provide the environment for a team to collaborate and organize work, and help you as a team lead or IT admin centrally set up security settings and govern usage and spend. You can create and manage a hub from the Azure portal or from the AI Studio.

In this article, you learn how to create and manage a hub in AI Studio with the default settings so you can get started quickly. Do you need to customize security or the dependent resources of your hub? Then use Azure portal or template options.

Tip

If you'd like to create your Azure AI Studio hub using a template, see the articles on using Bicep or Terraform.

Create a hub in AI Studio

To create a new hub, you need either the Owner or Contributor role on the resource group or on an existing hub. If you're unable to create a hub due to permissions, reach out to your administrator. If your organization is using Azure Policy, don't create the resource in AI Studio. Create the hub in the Azure portal instead.

Note

A hub in Azure AI Studio is a one-stop shop where you manage everything your AI project needs, like security and resources, so you can develop and test faster. To learn more about how hubs can help you, see the Hubs and projects overview article.

To create a hub in Azure AI Studio, follow these steps:

  1. Go to the Home page in Azure AI Studio and sign in with your Azure account.

  2. Select All resources on the left pane. If you cannot see this option, in the top bar select All resources & projects. Then select + New hub.

    Screenshot of the button to create a new hub.

  3. In the Create a new hub dialog, enter a name for your hub (such as contoso-hub). If you don't have a resource group, a new Resource group will be created linked to the Subscription provided. Leave the default Connect Azure AI Services option selected.

  4. Select Next. If you didn't reuse an existing resource group, a new resource group (rg-contoso) is created. Also an Azure AI service (ai-contoso-hub) is created for the hub.

    Screenshot of the dialog to connect services while creating a new hub.

    Note

    If you don't see (new) before the Resource group and Connect Azure AI Services entries then an existing resource is being used. For the purposes of this tutorial, create a separate entity via Create new resource group and Create new AI Services. This will allow you to prevent any unexpected charges by deleting the entities after the tutorial.

  5. Review the information and select Create.

    Screenshot of the dialog to review the settings for the new hub.

  6. You can view the progress of the hub creation in the wizard.

    Screenshot of the dialog to review the progress of hub resources creation.

Create a secure hub in the Azure portal

If your organization is using Azure Policy, set up a hub that meets your organization's requirements instead of using AI Studio for resource creation.

  1. From the Azure portal, search for Azure AI Studio and create a new hub by selecting + New Azure AI hub

  2. Enter your hub name, subscription, resource group, and location details.

  3. For Azure AI services base models, select an existing AI services resource or create a new one. Azure AI services include multiple API endpoints for Speech, Content Safety, and Azure OpenAI.

    Screenshot of the option to set hub basic information.

  4. Select the Storage tab to specify storage account settings. For storing credentials, either provide your Azure Key Vault or use the Microsoft-managed credential store (preview).

    Screenshot of the Create a hub with the option to set storage resource information.

  5. Select the Networking tab to set up Network isolation. Read more on network isolation. For a walkthrough of creating a secure hub, see Create a secure hub.

    Screenshot of the Create a hub with the option to set network isolation information.

  6. Select the Encryption tab to set up data encryption. You can either use Microsoft-managed keys or enable Customer-managed keys.

    Screenshot of the Create a hub with the option to select your encryption type.

  7. Select the Identity tab. By default, System assigned identity is enabled, but you can switch to User assigned identity if existing storage, key vault, and container registry are selected in Storage.

    Screenshot of the Create a hub with the option to select a managed identity.

    Note

    If you select User assigned identity, your identity needs to have the Cognitive Services Contributor role in order to successfully create a new hub.

  8. Select the Tags tab to add tags.

    Screenshot of the Create a hub with the option to add tags.

  9. Select Review + create > Create.

Manage your hub from the Azure portal

Manage access control

Manage role assignments from Access control (IAM) within the Azure portal. Learn more about hub role-based access control.

To add grant users permissions:

  1. Select + Add to add users to your hub.

  2. Select the Role you want to assign.

    Screenshot of the page to add a role within the Azure portal hub view.

  3. Select the Members you want to give the role to.

    Screenshot of the add members page within the Azure portal hub view.

  4. Review + assign. It can take up to an hour for permissions to be applied to users.

Networking

Hub networking settings can be set during resource creation or changed in the Networking tab in the Azure portal view. Creating a new hub invokes a Managed Virtual Network. This streamlines and automates your network isolation configuration with a built-in Managed Virtual Network. The Managed Virtual Network settings are applied to all projects created within a hub.

At hub creation, select between the networking isolation modes: Public, Private with Internet Outbound, and Private with Approved Outbound. To secure your resource, select either Private with Internet Outbound or Private with Approved Outbound for your networking needs. For the private isolation modes, a private endpoint should be created for inbound access. For more information on network isolation, see Managed virtual network isolation. To create a secure hub, see Create a secure hub.

At hub creation in the Azure portal, creation of associated Azure AI services, Storage account, Key vault (optional), Application insights (optional), and Container registry (optional) is given. These resources are found on the Resources tab during creation.

To connect to Azure AI services (Azure OpenAI, Azure AI Search, and Azure AI Content Safety) or storage accounts in Azure AI Studio, create a private endpoint in your virtual network. Ensure the public network access (PNA) flag is disabled when creating the private endpoint connection. For more about Azure AI services connections, follow documentation here. You can optionally bring your own (BYO) search, but this requires a private endpoint connection from your virtual network.

Encryption

Projects that use the same hub, share their encryption configuration. Encryption mode can be set only at the time of hub creation between Microsoft-managed keys and Customer-managed keys.

From the Azure portal view, navigate to the encryption tab, to find the encryption settings for your hub. For hubs that use CMK encryption mode, you can update the encryption key to a new key version. This update operation is constrained to keys and key versions within the same Key Vault instance as the original key.

Screenshot of the Encryption page of the hub in the Azure portal.

Update Azure Application Insights and Azure Container Registry

To use custom environments for Prompt Flow, you're required to configure an Azure Container Registry for your hub. To use Azure Application Insights for Prompt Flow deployments, a configured Azure Application Insights resource is required for your hub. Updating the workspace-attached Azure Container Registry or ApplicationInsights resources may break lineage of previous jobs, deployed inference endpoints, or your ability to rerun earlier jobs in the workspace.

You can use the Azure portal, Azure SDK/CLI options, or the infrastructure-as-code templates to update both Azure Application Insights and Azure Container Registry for the hub.

You can configure your hub for these resources during creation or update after creation.

To update Azure Application Insights from the Azure portal, navigate to the Properties for your hub in the Azure portal, then select Change Application Insights.

Screenshot of the properties page of the hub resource in the Azure portal.

Choose how credentials are stored

Select scenarios in AI Studio store credentials on your behalf. For example when you create a connection in AI Studio to access an Azure Storage account with stored account key, access Azure Container Registry with admin password, or when you create a compute instance with enabled SSH keys. No credentials are stored with connections when you choose EntraID identity-based authentication.

You can choose where credentials are stored:

  1. Your Azure Key Vault: This requires you to manage your own Azure Key Vault instance and configure it per hub. It gives you additional control over secret lifecycle e.g. to set expiry policies. You can also share stored secrets with other applications in Azure.

  2. Microsoft-managed credential store (preview): In this variant Microsoft manages an Azure Key Vault instance on your behalf per hub. No resource management is needed on your side and the vault does not show in your Azure subscription. Secret data lifecycle follows the resource lifecycle of your hubs and projects. For example, when a project's storage connection is deleted, its stored secret is deleted as well.

After your hub is created, it is not possible to switch between Your Azure Key Vault and using a Microsoft-managed credential store.

Delete an Azure AI Studio hub

To delete a hub from Azure AI Studio, select the hub and then select Delete hub from the Hub properties section of the page.

Screenshot of the delete hub link in hub properties.

Note

You can also delete the hub from the Azure portal.

Deleting a hub deletes all associated projects. When a project is deleted, all nested endpoints for the project are also deleted. You can optionally delete connected resources; however, make sure that no other applications are using this connection. For example, another Azure AI Studio deployment might be using it.