Merge pull request #295136 from whhender/February-Freshness-2025

February freshness 2025 - part 1

Author: denrea

articles/synapse-analytics/security/how-to-manage-synapse-rbac-role-assignments.md

@@ -5,7 +5,7 @@ author: meenalsri
 ms.service: azure-synapse-analytics
 ms.topic: how-to
 ms.subservice: security
-ms.date: 3/7/2022
+ms.date: 02/18/2025
 ms.author: mesrivas
 ms.reviewer: whhender, wiassaf
 ---
@@ -20,23 +20,23 @@ This article shows how to add and delete Synapse RBAC role assignments.
 >- To manage Synapse RBAC role assignments you need to have the Synapse Administrator role on the workspace or at a lower-level scope that includes the objects you want to manage. If you are a Synapse Administrator on the workspace you can grant access to all objects in the workspace. 
 >- **Guest users** from a different AD tenant can also see and manage role assignments after being assigned the Synapse Administrator role.
 >- To help you regain access to a workspace in the event that no Synapse Administrators are assigned or available to you, users with permissions to manage **Azure RBAC** role assignments on the workspace can also manage **Synapse RBAC** role assignments, allowing the addition of Synapse Administrator or other Synapse role assignments.
->- Access to SQL pools is managed using SQL permissions.  With the exception of the Synapse Administrator and Synapse SQL Administrator roles, Synapse RBAC roles do not grant access to SQL pools.
+>- Access to SQL pools is managed using SQL permissions. With the exception of the Synapse Administrator and Synapse SQL Administrator roles, Synapse RBAC roles do not grant access to SQL pools.
 
 >[!important]
 >- Changes made to Synapse RBAC role assignments may take 2-5 minutes to take effect. 
->- If you are managing Synapse RBAC permissions by modifying membership of security groups, then changes to membership are managed using Microsoft Entra ID.  Changes to group memberships may take 10-15 minutes or longer to take effect.
+>- If you are managing Synapse RBAC permissions by modifying membership of security groups, then changes to membership are managed using Microsoft Entra ID. Changes to group memberships may take 10-15 minutes or longer to take effect.
 
 ## Open Synapse Studio  
 
 To assign a role to a user, group, service principal, or managed identity, first [open the Synapse Studio](https://web.azuresynapse.net/) and log into your workspace. 
 
-![Log in to workspace](./media/common/login-workspace.png) 
- 
- Once you've opened your workspace, expand the **Security** section on the left and select **Access control**. 
+![Log in to workspace](./media/common/login-workspace.png)
+
+ In your workspace, expand the **Security** section on the left and select **Access control**.
 
  ![Select Access Control in Security section on left](./media/how-to-manage-synapse-rbac-role-assignments/left-nav-security-access-control.png)
 
-The Access control screen lists current role assignments.  You can filter the list by principal name or email, and  selectively filter the object types, roles, or scopes included. From this screen, you can add or remove role assignments.  
+The Access control screen lists current role assignments. You can filter the list by principal name or email, and  selectively filter the object types, roles, or scopes included. From this screen, you can add or remove role assignments.
 
 ## Add a Synapse role assignment
 
@@ -48,32 +48,32 @@ On the Add role assignment tab, you can create role assignments at workspace sco
 
 ## Add workspace-scoped role assignment
 
-First, select **Workspace** as the scope, then select the **Synapse RBAC role**.  Select the **principal(s)** to be assigned the role, then create the role assignment(s). 
+First, select **Workspace** as the scope, then select the **Synapse RBAC role**. Select the **principal(s)** to be assigned the role, then create the role assignment(s). 
 
 ![Add workspace role assignment - select role](./media/how-to-manage-synapse-rbac-role-assignments/access-control-workspace-role-assignment.png) 
 
 The assigned role will apply for all applicable objects in the workspace.
 
 ## Add workspace item-scoped role assignment
 
-To assign a role at a finer-grained scope, select **Workspace item** as the scope, then select the scoping **Item type**.       
+To assign a role at a finer-grained scope, select **Workspace item** as the scope, then select the scoping **Item type**.
 
 ![Add workspace item role assignment - select item type](./media/how-to-manage-synapse-rbac-role-assignments/access-control-add-workspace-item-assignment-select-item-type.png) 
 
-Select the specific **item** to be used as the scope, then select the **role** to be assigned from the drop-down.  The drop-down lists only those roles that are valid for the selected item type. [Learn more](./synapse-workspace-synapse-rbac.md).  
+Select the specific **item** to be used as the scope, then select the **role** to be assigned from the drop-down. The drop-down lists only those roles that are valid for the selected item type. [Learn more](./synapse-workspace-synapse-rbac.md). 
 
 ![Add workspace item role assignment - select role](./media/how-to-manage-synapse-rbac-role-assignments/access-control-add-workspace-item-assignment-select-role.png) 
 
-Then **select the principal(s)** to which the role is to be assigned.  You can iteratively select multiple principals.  Select **Apply** to create the role assignment(s).
+Then **select the principal(s)** to which the role is to be assigned. You can iteratively select multiple principals. Select **Apply** to create the role assignment(s).
 
 ## Remove a Synapse RBAC role assignment
 
-To revoke Synapse RBAC access, you remove the appropriate role assignments.  On the Access control screen, use the filters to locate the role assignment(s) to be removed.  Check the role assignments and then select **Remove access**.   
+To revoke Synapse RBAC access, you remove the appropriate role assignments. On the Access control screen, use the filters to locate the role assignment(s) to be removed. Check the role assignments and then select **Remove access**.
 
 ![Delete a role assignment to remove access](./media/how-to-manage-synapse-rbac-role-assignments/access-control-remove-access.png)
 
-Remember that changes to role assignments will take 2-5 minutes to take effect.   
+Remember that changes to role assignments will take 2-5 minutes to take effect.
 
-## Next steps
+## Related content
 
-[Understand the Synapse RBAC roles required to perform common tasks](./synapse-workspace-understand-what-role-you-need.md)
+[Understand the Synapse RBAC roles required to perform common tasks](./synapse-workspace-understand-what-role-you-need.md).

articles/synapse-analytics/security/media/how-to-manage-synapse-rbac-role-assignments/access-control-add.png

@@ -3,9 +3,9 @@ title: Azure Synapse role-based access control
 description: An article that explains role-based access control in Azure Synapse Analytics
 author: meenalsri
 ms.service: azure-synapse-analytics
-ms.topic: conceptual
+ms.topic: concept-article
 ms.subservice: security
-ms.date: 3/07/2022
+ms.date: 02/18/2025
 ms.author: mesrivas
 ms.reviewer: whhender, wiassaf
 ---
@@ -19,7 +19,7 @@ Synapse RBAC is used to manage who can:
 - Publish code artifacts and list or access published code artifacts, 
 - Execute code on Apaches Spark pools and Integration runtimes,
 - Access linked (data) services protected by credentials 
-- Monitor or cancel job execution, review job output, and execution logs.  
+- Monitor or cancel job execution, review job output, and execution logs. 
 
 >[!Note]
 >While Synapse RBAC is used to manage access to published SQL scripts, it provides only limited access control to serverless and dedicated SQL pools. Access to SQL pools is primarily controlled using SQL security.
@@ -30,10 +30,10 @@ Here are some examples of what you can do with Synapse RBAC:
   - Allow a user to publish changes made to Apache Spark notebooks and jobs to the live service.
   - Allow a user to run and cancel notebooks and spark jobs on a specific Apache Spark pool.
   - Allow a user to use specific credentials so they can run pipelines secured by the workspace system identity and access data in linked services secured with credentials. 
-  - Allow an administrator to manage, monitor, and cancel job execution on specific Spark Pools.    
+  - Allow an administrator to manage, monitor, and cancel job execution on specific Spark Pools.   
 
 ## How Synapse RBAC works
-Like Azure RBAC, Synapse RBAC works by creating role assignments. A role assignment consists of three elements: a security principal, a role definition, and a scope.  
+Like Azure RBAC, Synapse RBAC works by creating role assignments. A role assignment consists of three elements: a security principal, a role definition, and a scope. 
 
 ### Security Principals
 
@@ -47,13 +47,13 @@ Synapse provides built-in roles that define collections of actions that match th
 - Administrators can get full access to create and configure a workspace 
 - Developers can create, update and debug SQL scripts, notebooks, pipelines, and dataflows, but not be able to publish or execute this code on production compute resources/data
 - Operators can monitor and manage system status, application execution and review logs, without access to code or the outputs from execution.
-- Security staff can manage and configure endpoints without having access to code, compute resources or data.
+- Security staff can manage and configure endpoints without having access to code, compute resources, or data.
 
 [Learn more](./synapse-workspace-synapse-rbac-roles.md) about the built-in Synapse roles. 
 
 ### Scopes
 
-A _scope_ defines the resources or artifacts that the access applies to. Azure Synapse supports hierarchical scopes.  Permissions granted at a higher-level scope are inherited by objects at a lower level.  In Synapse RBAC, the top-level scope is a workspace.  Assigning a role with workspace scope grants permissions to all applicable objects in the workspace.  
+A _scope_ defines the resources or artifacts that the access applies to. Azure Synapse supports hierarchical scopes. Permissions granted at a higher-level scope are inherited by objects at a lower level. In Synapse RBAC, the top-level scope is a workspace. Assigning a role with workspace scope grants permissions to all applicable objects in the workspace. 
 
 Current supported scopes within a workspace are: 
 
@@ -62,23 +62,23 @@ Current supported scopes within a workspace are:
 - linked service
 - credential
 
-Access to code artifacts is granted with workspace scope.  Granting access to collections of artifacts within a workspace will be supported in a later release.
+Access to code artifacts is granted with workspace scope. Granting access to collections of artifacts within a workspace will be supported in a later release.
 
 ## Resolving role assignments to determine permissions
 
 A role assignment grants a principal the permissions defined by the role at the specified scope.
 
-Synapse RBAC is an additive model like Azure RBAC. Multiple roles may be assigned to a single principal and at different scopes. When computing the permissions of a security principal, the system considers all roles assigned to the principal and to groups that directly or indirectly include the principal.  It also considers the scope of each assignment in determining the permissions that apply.  
+Synapse RBAC is an additive model like Azure RBAC. Multiple roles may be assigned to a single principal and at different scopes. When computing the permissions of a security principal, the system considers all roles assigned to the principal and to groups that directly or indirectly include the principal. It also considers the scope of each assignment in determining the permissions that apply. 
 
 ## Enforcing assigned permissions
 
 In Synapse Studio, specific buttons or options may be grayed out or a permissions error may be returned when attempting an action if you don't have the required permissions. 
 
-If a button or option is disabled, hovering over the button or option shows a tooltip with the required permission.  Contact a Synapse Administrator to assign a role that grants the required permission. You can see the roles that provide specific actions, see [Synapse RBAC Roles](./synapse-workspace-synapse-rbac-roles.md).
+If a button or option is disabled, hovering over the button or option shows a tooltip with the required permission. Contact a Synapse Administrator to assign a role that grants the required permission. You can see the roles that provide specific actions, see [Synapse RBAC Roles](./synapse-workspace-synapse-rbac-roles.md).
 
 ## Who can assign Synapse RBAC roles?
 
-Synapse Administrators can assign Synapse RBAC roles.  A Synapse Administrator at the workspace level can grant access at any scope.  A Synapse Administrator at a lower-level scope can only grant access at that scope. 
+Synapse Administrators can assign Synapse RBAC roles. A Synapse Administrator at the workspace level can grant access at any scope. A Synapse Administrator at a lower-level scope can only grant access at that scope. 
 
 When a new workspace is created, the creator is automatically given the Synapse Administrator role at workspace scope.
 
@@ -88,10 +88,10 @@ To help you regain access to a workspace in the event that no Synapse Administra
 
 Synapse RBAC is managed from within Synapse Studio using the access control tools in the **Manage** hub. 
 
-## Next steps
+## Related content
 
 Understand the built-in [Synapse RBAC roles](./synapse-workspace-synapse-rbac-roles.md).
 
 Learn [how to review Synapse RBAC role assignments](./how-to-review-synapse-rbac-role-assignments.md) for a workspace.
 
-Learn [how to assign Synapse RBAC roles](./how-to-manage-synapse-rbac-role-assignments.md)
+Learn [how to assign Synapse RBAC roles](./how-to-manage-synapse-rbac-role-assignments.md).

articles/synapse-analytics/security/media/how-to-manage-synapse-rbac-role-assignments/access-control-remove-access.png

@@ -4,10 +4,10 @@ description: Table constraints support using dedicated SQL pool in Azure Synapse
 author: mstehrani
 ms.author: emtehran
 ms.reviewer: nibruno; wiassaf
-ms.date: 09/05/2019
+ms.date: 02/21/2025
 ms.service: azure-synapse-analytics
 ms.subservice: sql-dw
-ms.topic: conceptual
+ms.topic: concept-article
 ms.custom:
   - azure-synapse
 ---
@@ -19,23 +19,23 @@ Learn about table constraints in dedicated SQL pool, including primary key, fore
 ## Table constraints
 
 Dedicated SQL pool supports these table constraints: 
-- PRIMARY KEY is only supported when NONCLUSTERED and NOT ENFORCED are both used.    
+- PRIMARY KEY is only supported when NONCLUSTERED and NOT ENFORCED are both used.   
 - UNIQUE constraint is only supported when NOT ENFORCED is used.
 
 For syntax, check [ALTER TABLE](/sql/t-sql/statements/alter-table-transact-sql) and [CREATE TABLE](/sql/t-sql/statements/create-table-azure-sql-data-warehouse). 
 
-FOREIGN KEY constraint is not supported in dedicated SQL pool.  
+FOREIGN KEY constraint isn't supported in dedicated SQL pool. 
 
 
 ## Remarks
 
-Having primary key and/or unique key allows dedicated SQL pool engine to generate an optimal execution plan for a query.  All values in a primary key column or a unique constraint column should be unique.
+Having primary key and/or unique key allows dedicated SQL pool engine to generate an optimal execution plan for a query. All values in a primary key column or a unique constraint column should be unique.
 
 > [!IMPORTANT]  
 > After creating a table with primary key or unique constraint in dedicated SQL pool, users need to make sure all values in those columns are unique.
 > A violation of that may cause the query to return inaccurate result. 
 
-This example shows how a query may return inaccurate result if the primary key or unique constraint column includes duplicate values.  
+This example shows how a query may return inaccurate result if the primary key or unique constraint column includes duplicate values. 
 
 ```sql
  -- Create table t1
@@ -48,7 +48,7 @@ INSERT INTO t1 VALUES (2, 200)
 INSERT INTO t1 VALUES (3, 300)
 INSERT INTO t1 VALUES (4, 400)
 
--- Run this query.  No primary key or unique constraint.  4 rows returned. Correct result.
+-- Run this query. No primary key or unique constraint. 4 rows returned. Correct result.
 SELECT a1, COUNT(*) AS total FROM t1 GROUP BY a1
 
 /*
@@ -65,7 +65,7 @@ a1          total
 -- Add unique constraint
 ALTER TABLE t1 ADD CONSTRAINT unique_t1_a1 unique (a1) NOT ENFORCED
 
--- Re-run this query.  5 rows returned.  Incorrect result.
+-- Re-run this query. 5 rows returned. Incorrect result.
 SELECT a1, count(*) AS total FROM t1 GROUP BY a1
 
 /*
@@ -86,7 +86,7 @@ ALTER TABLE t1 DROP CONSTRAINT unique_t1_a1
 -- Add primary key constraint
 ALTER TABLE t1 add CONSTRAINT PK_t1_a1 PRIMARY KEY NONCLUSTERED (a1) NOT ENFORCED
 
--- Re-run this query.  5 rows returned.  Incorrect result.
+-- Re-run this query. 5 rows returned. Incorrect result.
 SELECT a1, COUNT(*) AS total FROM t1 GROUP BY a1
 
 /*
@@ -122,7 +122,7 @@ a1          b1
 -- Add unique constraint
 ALTER TABLE t1 add CONSTRAINT unique_t1_a1 UNIQUE (a1) NOT ENFORCED  
 
--- Re-run this query.  5 rows returned.  Correct result.
+-- Re-run this query. 5 rows returned. Correct result.
 SELECT a1, COUNT(*) as total FROM t1 GROUP BY a1
 
 /*
@@ -143,7 +143,7 @@ ALTER TABLE t1 DROP CONSTRAINT unique_t1_a1
 -- Add primary key constraint
 ALTER TABLE t1 ADD CONSTRAINT PK_t1_a1 PRIMARY KEY NONCLUSTERED (a1) NOT ENFORCED
 
--- Re-run this query.  5 rows returned.  Correct result.
+-- Re-run this query. 5 rows returned. Correct result.
 SELECT a1, COUNT(*) AS total FROM t1 GROUP BY a1
 
 /*
@@ -174,6 +174,6 @@ Create a dedicated SQL pool table with a unique constraint:
 CREATE TABLE t6 (c1 INT UNIQUE NOT ENFORCED, c2 INT);
 ```
 
-## Next steps
+## Related content
 
 After creating the tables for your dedicated SQL pool, the next step is to load data into the table. For a loading tutorial, see [Loading data to dedicated SQL pool](load-data-wideworldimportersdw.md).

articles/synapse-analytics/security/synapse-workspace-synapse-rbac.md

@@ -3,7 +3,7 @@ title: Best practices for dedicated SQL pools
 description: Recommendations and best practices you should know as you work with dedicated SQL pools.
 author: WilliamDAssafMSFT
 ms.author: wiassaf
-ms.date: 09/22/2022
+ms.date: 02/18/2025
 ms.service: azure-synapse-analytics
 ms.subservice: sql
 ms.topic: concept-article