Skip to content

Commit e64644e

Browse files
committed
Feature delay note
1 parent 4b628cf commit e64644e

2 files changed

Lines changed: 7 additions & 1 deletion

File tree

memdocs/intune/fundamentals/multi-admin-approval.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -29,6 +29,9 @@ ms.collection:
2929

3030
# Use Access policies to require multiple administrative approvals
3131

32+
> [!NOTE]
33+
> This feature is delayed and is not yet available. We'll remove this note when this feature beings to roll out to tenants.
34+
3235
*This feature is in Public Preview*
3336

3437
To help protect against a compromised administrative account, use Intune *access policies* to require that a second administrative account is used to approve a change before the change is applied. This capability is known as multiple administrative approval (MAA).

memdocs/intune/fundamentals/whats-new.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -236,7 +236,10 @@ For more information about protected apps, see [Microsoft Intune protected apps]
236236

237237
### Tenant administration
238238

239-
#### Access policies for Multiple Administrator Approval in public preview<!--9348867 -->
239+
#### Access policies for Multiple Administrator Approval in public preview<!--9348867 -->
240+
> [!NOTE]
241+
> This feature is delayed and is not yet available. We'll remove this note when this feature beings to roll out to tenants.
242+
240243
In public preview, you can use Intune *access policies* to require that a second Administrator Approval account be used to approve a change before the change is applied. This capability is known as multiple Administrator Approval (MAA).
241244

242245
You create an access policy to protect a type of resource, like App deployments. Each access policy also includes a group of users who are *approvers* for the changes protected by the policy. When a resource like an app deployment configuration is protected by an access policy, any changes that are made to the deployment, including creating, deleting or modifying an existing deployment won't apply until a member of the approvers group for that access policy reviews and approves that change.

0 commit comments

Comments
 (0)