Skip to content

Commit e9ca33c

Browse files
committed
Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into esanACS
2 parents 488f62a + fd91872 commit e9ca33c

File tree

407 files changed

+7917
-7692
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

407 files changed

+7917
-7692
lines changed

articles/ai-studio/how-to/costs-plan-manage.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -63,12 +63,15 @@ Before you delete an Azure AI hub resource in the Azure portal or with Azure CLI
6363
- Azure AI Search (for the data)
6464
- Virtual machines
6565
- Load Balancer
66-
- Virtual Network
66+
- Azure Virtual Network
6767
- Bandwidth
6868

6969
Each VM is billed per hour it's running. Cost depends on VM specifications. VMs that are running but not actively working on a dataset will still be charged via the load balancer. For each compute instance, one load balancer is billed per day. Every 50 nodes of a compute cluster have one standard load balancer billed. Each load balancer is billed around $0.33/day. To avoid load balancer costs on stopped compute instances and compute clusters, delete the compute resource.
7070

71-
Compute instances also incur P10 disk costs even in stopped state. This is because any user content saved there's persisted across the stopped state similar to Azure VMs. We're working on making the OS disk size/ type configurable to better control costs. For virtual networks, one virtual network is billed per subscription and per region. Virtual networks can't span regions or subscriptions. Setting up private endpoints in virtual network setups might also incur charges. Bandwidth is charged by usage; the more data transferred, the more you're charged.
71+
Compute instances also incur P10 disk costs even in stopped state. This is because any user content saved there's persisted across the stopped state similar to Azure VMs. We're working on making the OS disk size/ type configurable to better control costs. For Azure Virtual Networks, one virtual network is billed per subscription and per region. Virtual networks can't span regions or subscriptions. Setting up private endpoints in virtual network setups might also incur charges. If your virtual network uses an Azure Firewall, this might also incur charges. Bandwidth is charged by usage; the more data transferred, the more you're charged.
72+
73+
> [!TIP]
74+
> Using an managed virtual network is free. However some features of the managed network rely on Azure Private Link (for private endpoints) and Azure Firewall (for FQDN rules) and will incur charges. For more information, see [Managed virtual network isolation](configure-managed-network.md#pricing).
7275
7376
### Costs might accrue after resource deletion
7477

articles/aks/ingress-tls.md

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ ms.custom: devx-track-azurecli, devx-track-azurepowershell, linux-related-conten
77
author: asudbring
88
ms.author: allensu
99
ms.topic: how-to
10-
ms.date: 12/13/2023
10+
ms.date: 03/14/2024
1111
ROBOTS: NOINDEX
1212
#Customer intent: As a cluster operator or developer, I want to use TLS with an ingress controller to handle the flow of incoming traffic and secure my apps using my own certificates or automatically generated certificates.
1313
---
@@ -73,6 +73,9 @@ To use TLS with [Let's Encrypt][lets-encrypt] certificates, you'll deploy [cert-
7373
7474
* Use `Import-AzContainerRegistryImage` to import the following images into your ACR.
7575
76+
>[!NOTE]
77+
>When performing the steps to import the images into your ACR when working in Azure Government, you need to include the [`targetTag`][parameter-targettag] parameter with the value representing the tag of the image you want to import.
78+
7679
```azurepowershell
7780
$RegistryName = "<REGISTRY_NAME>"
7881
$ResourceGroup = (Get-AzContainerRegistry | Where-Object {$_.name -eq $RegistryName} ).ResourceGroupName
@@ -659,4 +662,5 @@ You can also:
659662
[acr-helm]: ../container-registry/container-registry-helm-repos.md
660663
[get-az-aks-cluster]: /powershell/module/az.aks/get-azakscluster
661664
[new-az-public-ip-address]: /powershell/module/az.network/new-azpublicipaddress
662-
[aks-app-add-on]: app-routing.md
665+
[aks-app-add-on]: app-routing.md
666+
[parameter-targettag]: /powershell/module/az.containerregistry/import-azcontainerregistryimage
9.47 KB
Loading

articles/azure-portal/set-preferences.md

Lines changed: 19 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Manage Azure portal settings and preferences
33
description: Change Azure portal settings such as default subscription/directory, timeouts, menu mode, contrast, theme, notifications, language/region and more.
4-
ms.date: 01/23/2024
4+
ms.date: 03/14/2024
55
ms.topic: how-to
66
---
77

@@ -146,13 +146,27 @@ Once you have made the desired changes to your language and regional format sett
146146

147147
## My information
148148

149-
**My information** lets you update the email address that is used for updates on Azure services, billing, support, or security issues. You can also opt in or out from additional emails about Microsoft Azure and other products and services.
149+
**My information** lets you provide information specific to your Azure experience.
150+
151+
### Email setting
152+
153+
The email address you provide here will be used if we need to contact you for updates on Azure services, billing, support, or security issues. You can change this address at any time.
154+
155+
Here, you can also indicate whether you'd like to receive additional emails about Microsoft Azure and other Microsoft products and services.
156+
157+
### Portal personalization
158+
159+
In this section, you can optionally share information about how you plan to use Azure. This information helps us provide tips, tools, and recommendations that are relevant to the tasks and services that you're interested in.
160+
161+
To provide this information, select one or more items from the list. You can change your selections at any time.
162+
163+
### Export, restore, and delete user settings
150164

151165
Near the top of **My information**, you'll see options to export, restore, or delete settings.
152166

153167
:::image type="content" source="media/set-preferences/settings-my-information.png" alt-text="Screenshot of My information settings." lightbox="media/set-preferences/settings-my-information.png":::
154168

155-
### Export user settings
169+
#### Export user settings
156170

157171
Information about your custom settings is stored in Azure. You can export the following user data:
158172

@@ -164,11 +178,11 @@ To export your portal settings, select **Export settings** from the top of the *
164178

165179
Due to the dynamic nature of user settings and risk of data corruption, you can't import settings from the JSON file. However, you can use this file to review the settings you selected. It can be useful to have a backup of your selections if you choose to delete your settings and private dashboards.
166180

167-
### Restore default settings
181+
#### Restore default settings
168182

169183
If you've made changes to the Azure portal settings and want to discard them, select **Restore default settings** from the top of the **My information** pane. You'll be prompted to confirm this action. When you do so, any changes you've made to your Azure portal settings will be lost. This option doesn't affect dashboard customizations.
170184

171-
### Delete user settings and dashboards
185+
#### Delete user settings and dashboards
172186

173187
Information about your custom settings is stored in Azure. You can delete the following user data:
174188

Lines changed: 148 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,148 @@
1+
---
2+
title: Configure Microsoft Intune Endpoint Privilege Management
3+
description: Learn how to configure Microsoft Intune Endpoint Privilege Management for dev boxes so that dev box users don't need local administrative privileges.
4+
author: RoseHJM
5+
ms.author: rosemalcolm
6+
ms.service: dev-box
7+
ms.topic: how-to
8+
ms.date: 02/27/2024
9+
10+
#customer intent: As a platform engineer, I want to configure elevated privilege management for dev boxes so that dev box users do not need local administrative privileges.
11+
---
12+
13+
# Configure Microsoft Intune Endpoint Privilege Management for dev boxes
14+
15+
In this article, you learn how to configure Microsoft Intune Endpoint Privilege Management (EPM) for dev boxes so that dev box users don't need local administrative privileges.
16+
17+
Microsoft Intune Endpoint Privilege Management allows your organization’s users to run as a standard user (without administrator rights) and complete tasks that require elevated privileges. Tasks that commonly require administrative privileges are application installs (like Microsoft 365 Applications), updating device drivers, and running certain Windows diagnostics.
18+
19+
Endpoint Privilege Management is built into Microsoft Intune, which means that all configuration is completed within the Microsoft Intune Admin Center. To get started with EPM, use the high-level process outlined as follows:
20+
21+
- *License Endpoint Privilege Management* - Before you can use Endpoint Privilege Management policies, you must license EPM in your tenant as an Intune add-on. For licensing information, see Use Intune Suite add-on capabilities.
22+
23+
- *Deploy an elevation settings policy* - An elevation settings policy activates EPM on the client device. This policy also allows you to configure settings that are specific to the client but aren't necessarily related to the elevation of individual applications or tasks.
24+
25+
## Prerequisites
26+
27+
- A dev center with a dev box project.
28+
- Microsoft Intune subscription.
29+
30+
## License Endpoint Privilege Management
31+
32+
Endpoint Privilege Management requires either a stand-alone license that adds only EPM, or license EPM as part of the Microsoft Intune Suite.
33+
34+
In this section, you configure EPM licensing and assign the EPM license to a user.
35+
36+
1. License EPM in your tenant as an Intune add-on:
37+
38+
1. Open the [Microsoft Intune admin center](https://intune.microsoft.com), and navigate to **Tenant admin** > **Intune add-ons**.
39+
1. Select **Endpoint Privilege Management**.
40+
41+
1. Configure Intune admin role for EPM administration:
42+
43+
1. In the Intune admin center, go to **Users**, and select the user you want to assign the role to.
44+
1. Select **Add assignments** and assign the **Global Administrator** role, and the **Intune Administrator** role.
45+
46+
:::image type="content" source="media/how-to-elevate-privilege-dev-box/tenant-admin.png" alt-text="Screenshot of the Microsoft Intune admin center, showing the available tenant admin roles." lightbox="media/how-to-elevate-privilege-dev-box/tenant-admin.png":::
47+
48+
1. Apply the EPM license in Microsoft 365:
49+
50+
In the [Microsoft 365 admin center](https://admin.microsoft.com/Adminportal/Home?#/catalog), go to **Billing** > **Purchase services** > **Endpoint Privilege Management**, and then select your EPM license.
51+
52+
1. Assign E5 and EPM licenses to target user in Microsoft Entra ID:
53+
54+
1. In the Intune admin center, go to **Users**, and select the user you want to assign the E5 and EPM licenses to.
55+
1. Select **Assignments** and assign the licenses.
56+
57+
:::image type="content" source="media/how-to-elevate-privilege-dev-box/assign-license.png" alt-text="Screenshot of the Microsoft Intune admin center, showing the available licenses." lightbox="media/how-to-elevate-privilege-dev-box/assign-license.png":::
58+
59+
## Deploy an elevation settings policy
60+
61+
A dev box must have an elevation settings policy that enables support for EPM to process an elevation rules policy or manage elevation requests. When support is enabled, the EPM Microsoft Agent, which processes the EPM policies, is installed.
62+
63+
In this section, you create a dev box and an Intune group that you use to test the EPM policy configuration. Then, you create an EPM elevation settings policy and assign the policy to the group.
64+
65+
1. Create a dev box definition
66+
67+
1. In the Azure portal, create a [dev box definition](how-to-manage-dev-box-definitions.md). Specify a supported OS, like *Windows 11, version 22H2*.
68+
69+
> [!NOTE]
70+
> EPM supports the following operating systems:
71+
> - Windows 11 (versions 23H2, 22H2, and 21H2)
72+
> - Windows 10 (versions 22H2, 21H2, and 20H2)
73+
74+
1. In your project, create a [dev box pool](how-to-manage-dev-box-pools.md) that uses the new dev box definition.
75+
76+
1. Assign [Dev Box User](how-to-dev-box-user.md) role to the test user.
77+
78+
1. Create a dev box for testing the policy
79+
80+
1. Sign in to the [developer portal](https://aka.ms/devbox-portal).
81+
82+
1. Create a dev box using the dev box pool you created in the previous step.
83+
84+
1. Determine the dev box hostname. You'll use this hostname add the dev box to and Intune group in the next step.
85+
86+
1. Create an Intune group and add the dev box to the group
87+
88+
1. Open the [Microsoft Intune admin center](https://intune.microsoft.com), select **Groups** > **New group**.
89+
90+
1. In the **Group type** dropdown box, select **Security**.
91+
92+
1. In the **Group name** field, enter the name for the new group (for example, Contoso Testers).
93+
94+
1. Add a **Group description** for the group.
95+
96+
1. Set the **Membership type** to **Assigned**.
97+
98+
1. Under **Members**, select the dev box you created.
99+
100+
1. Create an EPM elevation settings policy and assign it to the group.
101+
102+
1. In the Microsoft Intune admin center, select **Endpoint security** > **Endpoint Privilege Management** > **Policies** > **Create Policy**.
103+
104+
:::image type="content" source="media/how-to-elevate-privilege-dev-box/intune-endpoint-security.png" alt-text="Screenshot of Microsoft Intune admin center, showing the Endpoint security | Endpoint Privilege Management pane." lightbox="media/how-to-elevate-privilege-dev-box/intune-endpoint-security.png":::
105+
106+
1. In the **Create a profile** pane, select the following settings:
107+
- **Platform**: Windows 10 and later
108+
- **Profile type**: Elevation settings policy
109+
110+
1. On the **Basics** tab, enter a name for the policy.
111+
112+
:::image type="content" source="media/how-to-elevate-privilege-dev-box/create-profile-name.png" alt-text="Screenshot showing the Create profile basics tab with Policy name highlighted." lightbox="media/how-to-elevate-privilege-dev-box/create-profile-name.png":::
113+
114+
1. On the **Configuration settings** tab, in **Default elevation response**, select **Deny all elevation requests**.
115+
116+
:::image type="content" source="media/how-to-elevate-privilege-dev-box/deny-all-requests.png" alt-text="Screenshot showing the Configuration settings tab, with Endpoint Privilege Management enabled and Default elevation response set to Deny all requests." lightbox="media/how-to-elevate-privilege-dev-box/deny-all-requests.png":::
117+
118+
1. On the **Assignments** tab, select **Add groups**, add the group you created earlier, and then select **Create**.
119+
120+
:::image type="content" source="media/how-to-elevate-privilege-dev-box/assign-defined-group.png" alt-text="Screenshot showing the Create profile Assignments tab, with Add groups highlighted." lightbox="media/how-to-elevate-privilege-dev-box/assign-defined-group.png":::
121+
122+
## Verify administrative privilege restrictions
123+
124+
In this section, you validate that the Microsoft EPM Agent is installed and the policy is applied to the dev box.
125+
126+
1. Verify that the policy is applied to the dev box:
127+
128+
1. In the Microsoft Intune admin center, select **Devices** > the dev box you created earlier > **Device configuration** > the policy you created earlier.
129+
130+
:::image type="content" source="media/how-to-elevate-privilege-dev-box/intune-device-configuration.png" alt-text="Screenshot showing the Microsoft Intune admin center, with the Devices pane and Device configuration highlighted." lightbox="media/how-to-elevate-privilege-dev-box/intune-device-configuration.png":::
131+
132+
1. Wait until all the settings report as **Succeeded**.
133+
134+
:::image type="content" source="media/how-to-elevate-privilege-dev-box/device-profile-settings.png" alt-text="Screenshot showing the Profile Settings, with Setting status highlighted." lightbox="media/how-to-elevate-privilege-dev-box/device-profile-settings.png":::
135+
136+
1. Verify that the Microsoft EPM Agent is installed on the dev box:
137+
138+
1. Sign in to the dev box you created earlier.
139+
1. Navigate to *c:\Program Files*, and verify that a folder named **Microsoft EPM Agent** exists.
140+
141+
1. Attempt to run an application with administrative privileges.
142+
143+
On your dev box, right-click an application and select **Run with elevated access**. You receive a message that the installation is blocked.
144+
145+
## Related content
146+
147+
* [Use Intune Suite add-on capabilities](/mem/intune/fundamentals/intune-add-ons).
148+
* [Use Endpoint Privilege Management with Microsoft Intune](/mem/intune/protect/epm-overview).
33.6 KB
Loading
9.21 KB
Loading
20.2 KB
Loading
55.3 KB
Loading
26.9 KB
Loading

0 commit comments

Comments
 (0)