Skip to content

Commit 16aa8f4

Browse files
authored
Merge branch 'MicrosoftDocs:main' into maintenances
2 parents 4351038 + 6945060 commit 16aa8f4

File tree

2 files changed

+34
-0
lines changed

2 files changed

+34
-0
lines changed
Lines changed: 32 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,32 @@
1+
---
2+
title: Deny assignment policy for Service Fabric managed clusters
3+
description: An overview of the deny assignment policy for Service Fabric managed clusters.
4+
ms.topic: conceptual
5+
ms.author: tomcassidy
6+
author: tomvcassidy
7+
ms.service: service-fabric
8+
services: service-fabric
9+
ms.date: 08/18/2023
10+
---
11+
12+
# Deny assignment policy for Service Fabric managed clusters
13+
14+
Deny assignment policies for Service Fabric managed clusters enable customers to protect the resources of their clusters. Deny assignments attach a set of deny actions to a user, group, or service principal at a particular scope to deny access. Limiting access to certain actions can help users from inadvertently damaging their clusters when they delete, deallocate restart, or reimage their clusters' scale set directly in the infrastructure resource group, which can cause the resources of the cluster to be unsynchronized with the data in the managed cluster.
15+
16+
All actions that are related to managed clusters should be done through the managed cluster resource APIs instead of directly against the infrastructure resource group. Using the resource APIs ensures the resources of the cluster are synchronized with the data in the managed cluster.
17+
18+
This feature ensures that the correct, supported APIs are used when performing delete operations to avoid any errors.
19+
20+
You can learn more about deny assignments in the [Azure role-based access control (RBAC) documentation](../role-based-access-control/deny-assignments.md).
21+
22+
## Best practices
23+
24+
The following are some best practices to minimize the threat of desyncing your cluster's resources:
25+
* Instead of deleting virtual machine scale sets directly from the managed resource group, use NodeType level APIs to delete the NodeType or virtual machine scale set. Options include the Node blade on the Azure portal and [Azure PowerShell](/powershell/module/az.servicefabric/remove-azservicefabricmanagednodetype).
26+
* Use the correct APIs to restart or reimage your scale sets:
27+
* [Virtual machine scale set restarts](/powershell/module/az.servicefabric/restart-azservicefabricmanagednodetype)
28+
* [Virtual machine scale set reimage](/powershell/module/az.servicefabric/set-azservicefabricmanagednodetype)
29+
30+
## Next steps
31+
32+
* Learn more about [granting permission to access resources on managed clusters](how-to-managed-cluster-grant-access-other-resources.md)

articles/service-fabric/toc.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -413,6 +413,8 @@
413413
href: concepts-managed-identity.md
414414
- name: Configure container repository credentials
415415
href: configure-container-repository-credentials.md
416+
- name: Managed cluster deny assignment policy
417+
href: managed-cluster-deny-assignment.md
416418

417419
- name: How-to guides
418420
items:

0 commit comments

Comments
 (0)