Skip to content

Commit feeee5d

Browse files
authored
Merge pull request #8536 from MicrosoftDocs/main
Publish main to live on 9/26 @ 10:30 am
2 parents c7bb4d0 + 4a6793e commit feeee5d

3 files changed

Lines changed: 11 additions & 5 deletions

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 begins 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: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -141,7 +141,7 @@ Applies to:
141141
#### Device Firmware Configuration Interface (DFCI) now supports Acer devices<!-- 15240661 -->
142142
For Windows 10/11 devices, you can create a DFCI profile to manage UEFI (BIOS) settings (**Devices** > **Configuration profiles** > **Create profile** > **Windows 10 and later** for platform > **Templates** > **Device Firmware Configuration Interface** for profile type).
143143

144-
New Acer devices running Windows 10/11 will be enabled for DFCI starting Fall 2022. So, admins can create DFCI profiles to manage the BIOS and then deploy the profiles to these Acer devices.
144+
New Acer devices running Windows 10/11 will be enabled for DFCI in later 2022. So, admins can create DFCI profiles to manage the BIOS and then deploy the profiles to these Acer devices.
145145

146146
Contact your device vendor or device manufacturer to ensure you get eligible devices.
147147

@@ -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 begins 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.

memdocs/intune/protect/microsoft-tunnel-conditional-access.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -39,14 +39,14 @@ Before you can configure Conditional Access policies for the tunnel, you must en
3939

4040
2. Download the PowerShell script named **mst-ca-provisioning.ps1** from aka.ms/mst-ca-provisioning.
4141

42-
3. Using credentials that have the Azure Role permissions [equivalent to **Application Administrator**](/azure/active-directory/users-groups-roles/directory-assign-admin-roles#application-administrator-permissions), run the script from any location in your environment, to provision your tenant.
42+
3. Using credentials that have the Azure Role permissions [equivalent to **Global Administrator**](/azure/active-directory/roles/permissions-reference#global-administrator), run the script from any location in your environment, to provision your tenant.
4343

44-
The script modifies your tenant by creating a service principle with the following details:
44+
The script modifies your tenant by creating a service principal with the following details:
4545

4646
- App ID: 3678c9e9-9681-447a-974d-d19f668fcd88
4747
- Name: Microsoft Tunnel Gateway
4848

49-
The addition of this service principle is required so you can select the tunnel cloud app while configuring Conditional Access policies. It's also possible to use Graph to add the service principle information to your tenant.
49+
The addition of this service principal is required so you can select the tunnel cloud app while configuring Conditional Access policies. It's also possible to use Graph to add the service principal information to your tenant.
5050

5151
4. After the script completes, you can use your normal process to create Conditional Access policies.
5252

0 commit comments

Comments
 (0)