You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/active-directory/develop/howto-create-service-principal-portal.md
+9-9Lines changed: 9 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -36,9 +36,9 @@ Let's jump straight into creating the identity. If you run into a problem, check
36
36
37
37
You've created your Azure AD application and service principal.
38
38
39
-
## Assign the application to a role
39
+
## Assign a role to the application
40
40
41
-
To access resources in your subscription, you must assign the application to a role. Decide which role offers the right permissions for the application. To learn about the available roles, see [RBAC: Built in Roles](../../role-based-access-control/built-in-roles.md).
41
+
To access resources in your subscription, you must assign a role to the application. Decide which role offers the right permissions for the application. To learn about the available roles, see [RBAC: Built in Roles](../../role-based-access-control/built-in-roles.md).
42
42
43
43
You can set the scope at the level of the subscription, resource group, or resource. Permissions are inherited to lower levels of scope. For example, adding an application to the Reader role for a resource group means it can read the resource group and any resources it contains.
44
44
@@ -58,7 +58,7 @@ You can set the scope at the level of the subscription, resource group, or resou
58
58
59
59

60
60
61
-
1. Select **Save** to finish assigning the role. You see your application in the list of users assigned to a role for that scope.
61
+
1. Select **Save** to finish assigning the role. You see your application in the list of users with a role for that scope.
62
62
63
63
Your service principal is set up. You can start using it to run your scripts or apps. The next section shows how to get values that are needed when signing in programmatically.
64
64
@@ -108,7 +108,7 @@ If you choose not to use a certificate, you can create a new application secret.
108
108
1. Select **Client secrets -> New client secret**.
109
109
1. Provide a description of the secret, and a duration. When done, select **Add**.
110
110
111
-
After saving the client secret, the value of the client secret is displayed. Copy this value because you aren't able to retrieve the key later. You provide the key value with the application ID to sign in as the application. Store the key value where your application can retrieve it.
111
+
After saving the client secret, the value of the client secret is displayed. Copy this value because you won't be able to retrieve the key later. You will provide the key value with the application ID to sign in as the application. Store the key value where your application can retrieve it.
112
112
113
113

114
114
@@ -122,7 +122,7 @@ Keep in mind, you might need to configure addition permissions on resources that
122
122
123
123
## Required permissions
124
124
125
-
You must have sufficient permissions to register an application with your Azure AD tenant, and assign the application to a role in your Azure subscription.
125
+
You must have sufficient permissions to register an application with your Azure AD tenant, and assign to the application a role in your Azure subscription.
126
126
127
127
### Check Azure AD permissions
128
128
@@ -134,11 +134,11 @@ You must have sufficient permissions to register an application with your Azure
134
134
1. In the left pane, select **User settings**.
135
135
1. Check the **App registrations** setting. This value can only be set by an administrator. If set to **Yes**, any user in the Azure AD tenant can register an app.
136
136
137
-
If the app registrations setting is set to **No**, only users with an administrator role may register these types of applications. See [available roles](../users-groups-roles/directory-assign-admin-roles.md#available-roles) and [role permissions](../users-groups-roles/directory-assign-admin-roles.md#role-permissions) to learn about available administrator roles and the specific permissions in Azure AD that are given to each role. If your account is assigned to the User role, but the app registration setting is limited to admin users, ask your administrator to either assign you to one of the administrator roles that can create and manage all aspects of app registrations, or to enable users to register apps.
137
+
If the app registrations setting is set to **No**, only users with an administrator role may register these types of applications. See [available roles](../users-groups-roles/directory-assign-admin-roles.md#available-roles) and [role permissions](../users-groups-roles/directory-assign-admin-roles.md#role-permissions) to learn about available administrator roles and the specific permissions in Azure AD that are given to each role. If your account is assigned the User role, but the app registration setting is limited to admin users, ask your administrator to either assign you one of the administrator roles that can create and manage all aspects of app registrations, or to enable users to register apps.
138
138
139
139
### Check Azure subscription permissions
140
140
141
-
In your Azure subscription, your account must have `Microsoft.Authorization/*/Write` access to assign an AD app to a role. This action is granted through the [Owner](../../role-based-access-control/built-in-roles.md#owner) role or [User Access Administrator](../../role-based-access-control/built-in-roles.md#user-access-administrator) role. If your account is assigned to the **Contributor** role, you don't have adequate permission. You receive an error when attempting to assign the service principal to a role.
141
+
In your Azure subscription, your account must have `Microsoft.Authorization/*/Write` access to assign a role to an AD app. This action is granted through the [Owner](../../role-based-access-control/built-in-roles.md#owner) role or [User Access Administrator](../../role-based-access-control/built-in-roles.md#user-access-administrator) role. If your account is assigned the **Contributor** role, you don't have adequate permission. You will receive an error when attempting to assign the service principal a role.
142
142
143
143
To check your subscription permissions:
144
144
@@ -150,9 +150,9 @@ To check your subscription permissions:
150
150
151
151

152
152
153
-
1. Select **Role assignments** to view your assigned roles, and determine if you have adequate permissions to assign an AD app to a role. If not, ask your subscription administrator to add you to User Access Administrator role. In the following image, the user is assigned to the Owner role, which means that user has adequate permissions.
153
+
1. Select **Role assignments** to view your assigned roles, and determine if you have adequate permissions to assign a role to an AD app. If not, ask your subscription administrator to add you to User Access Administrator role. In the following image, the user is assigned the Owner role, which means that user has adequate permissions.
154
154
155
-

155
+

Create, read, update, and delete password reset user flows | B2C User Flow Administrator |
48
+
Create, read, update, and delete profile editing user flows | B2C User Flow Administrator |
49
+
Create, read, update, and delete sign-in user flows | B2C User Flow Administrator |
50
+
Create, read, update, and delete sign-up user flow |B2C User Flow Administrator |
51
+
Create, read, update, and delete user attributes | B2C User Flow Attribute Administrator |
52
+
Create, read, update, and delete users | User Administrator
53
53
Read all configuration | Global reader |
54
54
Read B2C audit logs | Global reader ([see documentation](https://docs.microsoft.com/azure/active-directory-b2c/active-directory-b2c-faqs)) |
55
55
@@ -124,7 +124,7 @@ Task | Least privileged role | Additional roles
124
124
---- | --------------------- | ----------------
125
125
Consent to any delegated permissions | Cloud application administrator | Application administrator
126
126
Consent to application permissions not including Microsoft Graph | Cloud application administrator | Application administrator
127
-
Consent to application permissions to Microsoft Graph | Global Administrator |
127
+
Consent to application permissions to Microsoft Graph | Privileged Role Administrator |
128
128
Consent to applications accessing own data | Default user role ([see documentation](https://docs.microsoft.com/azure/active-directory/fundamentals/users-default-permissions)) |
@@ -153,7 +153,7 @@ Assign license | User administrator |
153
153
Create group | User administrator |
154
154
Create, update, or delete access review of a group or of an app | User administrator |
155
155
Manage group expiration | User administrator |
156
-
Manage group settings | Global Administrator |
156
+
Manage group settings | Groups Administrator | User Administrator |
157
157
Read all configuration (except hidden membership) | Directory readers | Default user role ([see documentation](https://docs.microsoft.com/azure/active-directory/fundamentals/users-default-permissions))
158
158
Read hidden membership | Group member | Group owner, Password administrator, Exchange administrator, SharePoint administrator, Teams administrator, User administrator
159
159
Read membership of groups with hidden membership | Helpdesk Administrator | User administrator, Teams administrator
@@ -231,7 +231,7 @@ Read server status | Global reader |
231
231
232
232
Task | Least privileged role | Additional roles
233
233
---- | --------------------- | ----------------
234
-
Manage identity providers | Global Administrator |
@@ -327,11 +327,11 @@ Create user | User administrator |
327
327
Delete users | User administrator |
328
328
Invalidate refresh tokens of limited admins (see documentation) | User administrator |
329
329
Invalidate refresh tokens of non-admins (see documentation) | Password administrator | User administrator
330
-
Invalidate refresh tokens of privileged admins (see documentation) | Global Administrator |
330
+
Invalidate refresh tokens of privileged admins (see documentation) | Privileged Authentication Administrator |
331
331
Read basic configuration | Default User role ([see documentation](https://docs.microsoft.com/azure/active-directory/fundamentals/users-default-permissions) |
332
332
Reset password for limited admins (see documentation) | User administrator |
333
333
Reset password of non-admins (see documentation) | Password administrator | User administrator
334
-
Reset password of privileged admins | Global Administrator |
334
+
Reset password of privileged admins | Privileged Authentication Administrator |
335
335
Revoke license | License administrator | User administrator
336
336
Update all properties except User Principal Name | User administrator |
337
337
Update User Principal Name for limited admins (see documentation) | User administrator |
Copy file name to clipboardExpand all lines: articles/aks/azure-netapp-files.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,7 +29,8 @@ The following limitations apply when you use Azure NetApp Files:
29
29
* Azure NetApp Files is only available [in selected Azure regions][anf-regions].
30
30
* Before you can use Azure NetApp Files, you must be granted access to the Azure NetApp Files service. To apply for access, you can use the [Azure NetApp Files waitlist submission form][anf-waitlist]. You can't access the Azure NetApp Files service until you receive the official confirmation email from the Azure NetApp Files team.
31
31
* Your Azure NetApp Files service must be created in the same virtual network as your AKS cluster.
32
-
* Only static provisioning for Azure NetApp Files is supported on AKS.
32
+
* After the initial deployment of an AKS cluster, only static provisioning for Azure NetApp Files is supported.
33
+
* To use dynamic provisioning with Azure NetApp Files, install and configure [NetApp Trident](https://netapp-trident.readthedocs.io/) version 19.07 or later.
Copy file name to clipboardExpand all lines: articles/data-factory/quickstart-create-data-factory-dot-net.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -43,7 +43,7 @@ From the sections in *How to: Use the portal to create an Azure AD application a
43
43
1. In [Create an Azure Active Directory application](../active-directory/develop/howto-create-service-principal-portal.md#create-an-azure-active-directory-application), create an application that represents the .NET application you are creating in this tutorial. For the sign-on URL, you can provide a dummy URL as shown in the article (`https://contoso.org/exampleapp`).
44
44
2. In [Get values for signing in](../active-directory/develop/howto-create-service-principal-portal.md#get-values-for-signing-in), get the **application ID** and **tenant ID**, and note down these values that you use later in this tutorial.
45
45
3. In [Certificates and secrets](../active-directory/develop/howto-create-service-principal-portal.md#certificates-and-secrets), get the **authentication key**, and note down this value that you use later in this tutorial.
46
-
4. In [Assign the application to a role](../active-directory/develop/howto-create-service-principal-portal.md#assign-the-application-to-a-role), assign the application to the **Contributor** role at the subscription level so that the application can create data factories in the subscription.
46
+
4. In [Assign the application to a role](../active-directory/develop/howto-create-service-principal-portal.md#assign-a-role-to-the-application), assign the application to the **Contributor** role at the subscription level so that the application can create data factories in the subscription.
Copy file name to clipboardExpand all lines: articles/virtual-machines/windows/sizes.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,7 +20,7 @@ ms.author: jonbeck
20
20
21
21
# Sizes for Windows virtual machines in Azure
22
22
23
-
This article describes the available sizes and options for the Azure virtual machines you can use to run your Windows apps and workloads. It also provides deployment considerations to be aware of when you're planning to use these resources. This article is also available for [Linux virtual machines](/linux/sizes.md?toc=%2fazure%2fvirtual-machines%2flinux%2ftoc.json).
23
+
This article describes the available sizes and options for the Azure virtual machines you can use to run your Windows apps and workloads. It also provides deployment considerations to be aware of when you're planning to use these resources. This article is also available for [Linux virtual machines](../linux/sizes.md).
24
24
25
25
| Type | Sizes | Description |
26
26
|------|-------|-------------|
@@ -62,4 +62,4 @@ Learn more about the different VM sizes that are available:
62
62
-[Storage optimized](../sizes-storage.md)
63
63
-[GPU optimized](../sizes-gpu.md)
64
64
-[High performance compute](../sizes-hpc.md)
65
-
- Check the [Previous generation](../sizes-previous-gen.md) page for A Standard, Dv1 (D1-4 and D11-14 v1), and A8-A11 series
65
+
- Check the [Previous generation](../sizes-previous-gen.md) page for A Standard, Dv1 (D1-4 and D11-14 v1), and A8-A11 series
Copy file name to clipboardExpand all lines: includes/cdn-app-dev-prep.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -35,7 +35,7 @@ Creating a service principal consists of several steps, including creating an Az
35
35
>
36
36
> When you get to the step named Configure multi-tenant application, select **No**.
37
37
>
38
-
> When you get to the step [Assign the application to a role](../articles/active-directory/develop/howto-create-service-principal-portal.md#assign-the-application-to-a-role), use the resource group created earlier, *CdnConsoleTutorial*, but instead of the **Reader** role, assign the **CDN Profile Contributor** role. After you assign the application the **CDN Profile Contributor** role on your resource group, return to this tutorial.
38
+
> When you get to the step [Assign the application to a role](../articles/active-directory/develop/howto-create-service-principal-portal.md#assign-a-role-to-the-application), use the resource group created earlier, *CdnConsoleTutorial*, but instead of the **Reader** role, assign the **CDN Profile Contributor** role. After you assign the application the **CDN Profile Contributor** role on your resource group, return to this tutorial.
0 commit comments