Skip to content

Contact sales

By filling out this form and clicking submit, you acknowledge our privacy policy.
  • Labs icon Lab
  • A Cloud Guru
Azure icon
Labs

Configure Azure Private Link for Blob Storage

Private Link is an Azure service that helps provide private network accessibility to a range of supported services. Private Link supports several Azure PaaS solutions, as well as customer-managed solutions (backed by a standard load balancer). In this lab, you will have the opportunity to configure the Private Link service for Azure Blob storage. This will enable private connectivity between a virtual machine and Blob storage, within a virtual network. After completing this lab, you'll be familiar with how to configure a Private Endpoint for the Azure Blob service, using Private Link. **Note:** In the lab, use the `West US` for the creation of resources.

Azure icon
Labs

Path Info

Level
Clock icon Intermediate
Duration
Clock icon 1h 0m
Published
Clock icon Jun 05, 2020

Contact sales

By filling out this form and clicking submit, you acknowledge our privacy policy.

Table of Contents

  1. Challenge

    Configure a Private Endpoint for Blob Storage

    Log in to the Azure portal using the credentials provided in the lab.

    Navigate to the storage account that was created for this lab, and create a new private endpoint called privatelink1 in the West US region that uses the existing resource group and hands-on lab subscription. Set the Target sub-resource to blob, the Virtual network to vnet1, and the Subnet to subnet1.

  2. Challenge

    Verify the Private Endpoint from VM1

    Copy the details for the blob endpoint:

    1. Navigate to the storage account that was created for the lab.
    2. On the left-side menu, navigate to Endpoints (under Settings), and copy the FQDN without copying https:// or the trailing slash / (e.g., azurelalab123.blob.core.windows.net).
    3. Open a terminal session, and use nslookup followed by the FQDN you copied to see a public IP address

    Connect to vm1 using RDP:

    1. Navigate to the Virtual Machines service page.
    2. Select vm1, and connect using RDP. You can use the RDP file, downloaded from the Azure portal, with your preferred RDP client. You can also copy the public IP address for vm1 from your lab credentials and connect via RDP manually with your RDP client. The username and password for vm1 are provided in your lab credentials.

    Verify the private endpoint from vm1:

    1. From the RDP session, open a command prompt.
    2. Use nslookup (along with the FQDN from earlier) to verify the DNS now points to a private IP address.

The Cloud Content team comprises subject matter experts hyper focused on services offered by the leading cloud vendors (AWS, GCP, and Azure), as well as cloud-related technologies such as Linux and DevOps. The team is thrilled to share their knowledge to help you build modern tech solutions from the ground up, secure and optimize your environments, and so much more!

What's a lab?

Hands-on Labs are real environments created by industry experts to help you learn. These environments help you gain knowledge and experience, practice without compromising your system, test without risk, destroy without fear, and let you learn from your mistakes. Hands-on Labs: practice your skills before delivering in the real world.

Provided environment for hands-on practice

We will provide the credentials and environment necessary for you to practice right within your browser.

Guided walkthrough

Follow along with the author’s guided walkthrough and build something new in your provided environment!

Did you know?

On average, you retain 75% more of your learning if you get time for practice.

Start learning by doing today

View Plans