opomba,
Dostop do te strani zahteva pooblastilo. Poskusite se vpisati alispremeniti imenike.
Dostop do te strani zahteva pooblastilo. Poskusite lahko spremeniti imenike.
During local development, applications need to authenticate to Azure to use different Azure services. Authenticate locally by using one of these approaches:
- Use a developer account with one of the developer tools supported by the Azure Identity library.
- Use a service principal.
This article explains how to authenticate by using a developer account with tools supported by the Azure Identity library. In the following sections, you learn:
- How to use Microsoft Entra groups to efficiently manage permissions for multiple developer accounts.
- How to assign roles to developer accounts to scope permissions.
- How to sign in to supported local development tools.
- How to authenticate by using a developer account from your app code.
Supported developer tools for authentication
For an app to authenticate to Azure during local development by using the developer's Azure credentials, the developer must be signed in to Azure from one of the following developer tools:
- Azure CLI
- Azure Developer CLI
The Azure Identity library can detect that the developer is signed in from one of these tools. The library can then obtain the Microsoft Entra access token via the tool to authenticate the app to Azure as the signed-in user.
This approach takes advantage of the developer's existing Azure accounts to streamline the authentication process. However, a developer's account likely has more permissions than required by the app, therefore exceeding the permissions the app runs with in production. As an alternative, you can create application service principals to use during local development, which can be scoped to have only the access needed by the app.
Create a Microsoft Entra group for local development
Create a Microsoft Entra group to encapsulate the roles (permissions) the app needs in local development rather than assigning the roles to individual service principal objects. This approach offers the following advantages:
- Every developer has the same roles assigned at the group level.
- If a new role is needed for the app, it only needs to be added to the group for the app.
- If a new developer joins the team, a new application service principal is created for the developer and added to the group, ensuring the developer has the right permissions to work on the app.
Navigate to the Microsoft Entra ID overview page in the Azure portal.
Select All groups from the left-hand menu.
On the Groups page, select New group.
On the New group page, fill out the following form fields:
- Group type: Select Security.
- Group name: Enter a name for the group that includes a reference to the app or environment name.
- Group description: Enter a description that explains the purpose of the group.
Select the No members selected link under Members to add members to the group.
In the flyout panel that opens, search for the service principal you created earlier and select it from the filtered results. Choose the Select button at the bottom of the panel to confirm your selection.
Select Create at the bottom of the New group page to create the group and return to the All groups page. If you don't see the new group listed, wait a moment and refresh the page.
Assign roles to the group
Next, determine what roles (permissions) your app needs on what resources and assign those roles to the Microsoft Entra group you created. Groups can be assigned a role at the resource, resource group, or subscription scope. This example shows how to assign roles at the resource group scope, since most apps group all their Azure resources into a single resource group.
In the Azure portal, navigate to the Overview page of the resource group that contains your app.
Select Access control (IAM) from the left navigation.
On the Access control (IAM) page, select + Add and then choose Add role assignment from the drop-down menu. The Add role assignment page provides several tabs to configure and assign roles.
On the Role tab, use the search box to locate the role you want to assign. Select the role, and then choose Next.
On the Members tab:
- For the Assign access to value, select User, group, or service principal .
- For the Members value, choose + Select members to open the Select members flyout panel.
- Search for the Microsoft Entra group you created earlier and select it from the filtered results. Choose Select to select the group and close the flyout panel.
- Select Review + assign at the bottom of the Members tab.
On the Review + assign tab, select Review + assign at the bottom of the page.
Sign in to Azure by using developer tooling
Next, sign in to Azure by using one of the developer tools that you can use to perform authentication in your development environment. The account you authenticate should also exist in the Microsoft Entra group you created and configured earlier.
Developers can use Azure CLI to authenticate. Apps that use DefaultAzureCredential or AzureCLICredential can then use this account to authenticate app requests.
To authenticate with the Azure CLI, run the az login command. On a system with a default web browser, the Azure CLI launches the browser to authenticate the user.
az login
For systems without a default web browser, the az login command uses the device code authentication flow. You can also force the Azure CLI to use the device code flow rather than launching a browser by specifying the --use-device-code argument.
az login --use-device-code
Authenticate to Azure services from your app
The azure_identity crate provides various credentials adapted to support different scenarios and Microsoft Entra authentication flows. The following steps demonstrate how to use DeveloperToolsCredential or specific tool credentials when working locally.
Implement the code
To authenticate Azure SDK client objects to Azure, your application should use a credential from the azure_identity crate. DeveloperToolsCredential attempts to authenticate by using a series of developer tools such as the Azure CLI, and stops when one succeeds.
Add the
azure_identitycrate to your project.cargo add azure_identityFor any Rust code that creates an Azure SDK client object, you want to:
- Import the
azure_identitycrate. - Create an instance of
DeveloperToolsCredentialor a specific tool credential. - Pass the credential instance to the Azure SDK client constructor.
To use
DeveloperToolsCredential, which tries Azure CLI and Azure Developer CLI in sequence:use azure_identity::DeveloperToolsCredential; fn main() -> Result<(), Box<dyn std::error::Error>> { let credential = DeveloperToolsCredential::new(None)?; Ok(()) }Or use a specific credential such as
AzureCliCredentialorAzureDeveloperCliCredential:use azure_identity::AzureCliCredential; fn main() -> Result<(), Box<dyn std::error::Error>> { let credential = AzureCliCredential::new(None)?; // or // use azure_identity::AzureDeveloperCliCredential; // let credential = AzureDeveloperCliCredential::new(None)?; Ok(()) }
- Import the
The following example demonstrates authenticating a Key Vault SecretClient by using DeveloperToolsCredential:
use azure_identity::DeveloperToolsCredential;
use azure_security_keyvault_secrets::SecretClient;
#[tokio::main]
async fn main() -> Result<(), Box<dyn std::error::Error>> {
// Create a credential
let credential = DeveloperToolsCredential::new(None)?;
// Create a client for the specified Key Vault
let client = SecretClient::new(
"https://<your-key-vault-name>.vault.azure.net/",
credential.clone(),
None,
)?;
// Use the client to interact with Azure Key Vault
// let secret = client.get("secret-name", None).await?;
Ok(())
}