Connect BareMetal Infrastructure instances in Azure

You'll need to list your subscription in the Azure portal and then double-click the subscription used to deploy your BareMetal instances.

1. Sign in to the Azure portal.

2. On the Azure portal menu, select All services.

3. In the All services box, enter subscription, and then select Subscriptions.

4. Select the subscription from the subscription list.

5. Select Resource providers and enter BareMetalInfrastructure into search. The resource provider should be Registered, as the image shows.

To begin using Azure CLI:

• Use the Bash environment in Azure Cloud Shell. For more information, see Quickstart for Bash in Azure Cloud Shell.

  

• If you prefer to run CLI reference commands locally, install the Azure CLI. If you're running on Windows or macOS, consider running Azure CLI in a Docker container. For more information, see How to run the Azure CLI in a Docker container.

  • If you're using a local installation, sign in to the Azure CLI by using the az login command. To finish the authentication process, follow the steps displayed in your terminal. For other sign-in options, see Sign in with the Azure CLI.

  • When you're prompted, install the Azure CLI extension on first use. For more information about extensions, see Use extensions with the Azure CLI.

  • Run az version to find the version and dependent libraries that are installed. To upgrade to the latest version, run az upgrade.

Sign in to the Azure subscription you use for the BareMetal instance deployment through the Azure CLI. Register the BareMetalInfrastructure resource provider with the az provider register command:

az provider register --namespace Microsoft.BareMetalInfrastructure

You can use the az provider list command to see all available providers.

1. In the Azure portal, in the BareMetal subscription, select Resource groups.

   

2. In the list, locate the new resource group.

   

   Tip

   You can filter on the subscription you used to deploy the BareMetal instance. After you filter to the proper subscription, you might have a long list of resource groups. Look for one with a post-fix of -Txxx where xxx is three digits like -T250.

3. Select the new resource group to view its details. The image shows one BareMetal instance deployed.

   Note

   If you deployed several BareMetal instance tenants under the same Azure subscription, you will see multiple Azure resource groups.

To see all your BareMetal instances, run the az baremetalinstance list command for your resource group:

az baremetalinstance list --resource-group DSM05A-T550 –output table

In the list of BareMetal instances, select the single instance you want to view.

The attributes in the image don't look much different than the Azure virtual machine (VM) attributes. On the left, you'll see the Resource group, Azure region, and subscription name and ID. If you assigned tags, you'll see them here as well. By default, the BareMetal instances don't have tags assigned.

On the right, you'll see the name of the BareMetal instance, operating system (OS), IP address, and SKU that shows the number of CPU threads and memory. You'll also see the power state and hardware version (revision of the BareMetal instance stamp). The power state indicates whether the hardware unit is powered on or off. The operating system details, however, don't indicate whether it's up and running.

The possible hardware revisions are:

• Revision 3 (Rev 3)

• Revision 4 (Rev 4)

• Revision 4.2 (Rev 4.2)

Also on the right side, you'll find the Azure proximity placement group's name. The placement group's name is created automatically for each deployed BareMetal instance. Reference the proximity placement group when you deploy the Azure VMs that host the application layer. Use the proximity placement group associated with the BareMetal instance to ensure the Azure VMs are deployed close to the BareMetal instance.

To see these details of a BareMetal instance, run the az baremetalinstance show command:

az baremetalinstance show --resource-group DSM05A-T550 --instance-name orcllabdsm01

If you're uncertain of the instance name, run the az baremetalinstance list command, described above.

You can add Azure tags to a BareMetal instance or delete them. Tags get assigned just as they do when assigning tags to VMs. As with VMs, the tags exist in the Azure metadata. Tags have the same restrictions for BareMetal instances as for VMs.

Deleting tags also works the same way as for VMs. Both applying and deleting a tag is listed in the BareMetal instance's Activity log.

Assigning tags to BareMetal instances works the same as assigning tags for virtual machines. As with VMs, the tags exist in the Azure metadata. Tags have the same restrictions for BareMetal instances as for VMs.

To add tags to a BareMetal instance, run the az baremetalinstance update command:

az baremetalinstance update --resource-group DSM05a-T550 --instance-name orcllabdsm01 --set tags.Dept=Finance tags.Status=Normal

Use the same command to remove a tag:

az baremetalinstance update --resource-group DSM05a-T550 --instance-name orcllabdsm01 --remove tags.Dept

You can do a power restart of the instance directly from the Azure portal:

Select Restart and then Yes to confirm the restart.

When you restart a BareMetal instance, you'll experience a delay. During this delay, the power state moves from Starting to Started, which means the OS has started up completely. As a result, after a restart, you can only log into the unit once the state switches to Started.

To restart a BareMetal instance, use the az baremetalinstance restart command:

az baremetalinstance restart --resource-group DSM05a-T550 --instance-name orcllabdsm01