Skip to content

Microsoft Azure Data Engineering Associate (DP-203) Study Guide

Menu
  • Contact Us
Menu

ACCESS CONTROL – Data Sources and Ingestion

Posted on 2023-05-302024-08-05 by Benjamin Goodwin

This feature enables you to grant individuals access to either the Azure Synapse Analytics workspace or a single workspace item. When you initially access the Access Control page, you will see something similar to Figure 3.39.

The Access Control page lists the user accounts grouped by Synapse RBAC roles, the type of account, the role, and the scope. Only users who have an account configured into the Azure Active Directory tenant where the Azure Synapse Analytics workspace was provisioned can be granted access. That means user accounts or service principal accounts that meet that requirement will render in the Select User search box, as shown in Figure 3.40. Synapse RBAC roles were introduced in Chapter 1, but you can see some examples such as Synapse Administrator, Synapse SQL Administrator, and Synapse Compute Operator. Each of those roles has a different level of resource permissions, such as reading, writing, or deleting data, making configurations to compute pools, or provisioning new workspace resources. There is a link to all the Synapse roles in Chapter 1.

FIGUER 3.39 The Access Control page in Azure Synapse Analytics

FIGUER 3.40 Adding a role assignment in Azure Synapse Analytics

The different user types can be either a user, a group, or a service principle. Notice that there is a service principle with the same name as the Azure Synapse Analytics workspace. That identity is what is used to grant the workspace access to other Azure resources. For example, in the Azure portal navigate to the ADLS account that you configured when provisioning the Azure Synapse Analytics workspace in Exercise 3.3. Click the Access Control (IAM) link in the navigation menu, and then click the Role Assignments tab. You will see that service principle has been granted access. The service principle is part of the Storage Blob Data Container role. The data in the Scope column, in Synapse Studio, identifies whether the user or service principal account has access to the workspace or a specific item within the workspace. Most of Chapter 8 has to do with security, so if you are interested in that topic now, consider skipping forward (but do come back).

CREDENTIALS

As of this writing, the features available from the Credentials menu item are in preview. This feature has to do with managed identities. As mentioned in the previous section, the Azure Synapse Analytics workspace generates a service principal account, which is used for gaining access to other Azure resources. This feature provides the interface to grant user‐assigned, systems‐assigned managed identities and service principals permission to access the workspace. There is a twist, though. This identity is used in collaboration with resources configured in the Linked Services area. For other resources in the workspace, you can use the capabilities provided via Access Control.

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Archives

  • August 2024
  • July 2024
  • June 2024
  • May 2024
  • March 2024
  • February 2024
  • January 2024
  • December 2023
  • November 2023
  • October 2023
  • September 2023
  • August 2023
  • June 2023
  • May 2023
  • April 2023
  • March 2023
  • February 2023
  • January 2023
  • December 2022
  • November 2022
  • October 2022
  • July 2022
  • May 2022
  • March 2022
  • February 2022
  • January 2022
  • December 2021
  • November 2021
  • October 2021
  • September 2021
  • May 2021

Categories

  • ARM TEMPLATE
  • Create an Azure Data Factory
  • DATA EXPLORER POOLS
  • Design Analytical Stores
  • MANAGED PRIVATE ENDPOINTS
  • Microsoft DP-203
© 2025 Microsoft Azure Data Engineering Associate (DP-203) Study Guide All Rights Reserved