Merge pull request MicrosoftDocs#257 from Azure/Graham71046

Bug 71046 ver3.7

Author: Graham Priestley

azureps-cmdlets-docs/ResourceManager/AzureRM.Resources/v3.7.0/New-AzureRmRoleAssignment.md

@@ -82,76 +82,77 @@ New-AzureRmRoleAssignment -ServicePrincipalName <String> [-Scope <String>] -Role
 ```
 
 ## DESCRIPTION
-Use the New-AzureRMRoleAssignment command to grant access.
+The **New-AzureRMRoleAssignment** cmdlet assigns the specified RBAC role to the specified principal, at the specified scope.
+
 Access is granted by assigning the appropriate RBAC role to them at the right scope.
 To grant access to the entire subscription, assign a role at the subscription scope.
 To grant access to a specific resource group within a subscription, assign a role at the resource group scope.
 
 The subject of the assignment must be specified.
-To specify a user, use SignInName or Azure AD ObjectId parameters.
-To specify a security group, use Azure AD ObjectId parameter.
-And to specify an Azure AD application, use ServicePrincipalName or ObjectId parameters.
+To specify a user, use the *SignInName* or *ObjectId* parameters.
+To specify a security group, use the *ObjectId* parameter.
+And to specify an Azure AD application, use the *ServicePrincipalName* or *ObjectId* parameters.
 
-The role that is being assigned must be specified using the RoleDefinitionName parameter.
+The role that is being assigned must be specified using the *RoleDefinitionName* parameter.
 
 The scope at which access is being granted may be specified.
 It defaults to the selected subscription. 
-The scope of the assignment can be specified using one of the following parameter combinations
-        a.
-Scope - This is the fully qualified scope starting with /subscriptions/\<subscriptionId\>
-        b.
-ResourceGroupName - to grant access to the specified resource group.
-        c.
-ResourceName, ResourceType, ResourceGroupName and (optionally) ParentResource - to specify a particular resource within a resource group to grant access to.
+The scope of the assignment can be specified using one of the following parameter combinations:
+        
+- *Scope* - This is the fully qualified scope starting with /subscriptions/\<subscriptionId\>
+
+- *ResourceGroupName* - to grant access to the specified resource group.
+
+- *ResourceName*, *ResourceType*, *ResourceGroupName*, and *ParentResource* - to specify a particular resource within a resource group to grant access to.
 
 ## EXAMPLES
 
-### Example 1:
+### Example 1: Grant reader role access to a user
 
 
 ```
-PS C:\> New-AzureRmRoleAssignment -ResourceGroupName rg1 -SignInName allen.young@live.com -RoleDefinitionName Reader
+PS C:\> New-AzureRmRoleAssignment -ResourceGroupName rg1 -SignInName "patti.fuller@contoso.com" -RoleDefinitionName Reader
 ```
 
-Grant Reader role access to a user at a resource group scope
+This command grants reader role access to a user at a resource group scope.
 
-### Example 2:
+### Example 2: Grant access to a security group
 
 
 ```
-PS C:\> Get-AzureRMADGroup -SearchString "Christine Koch Team"
+PS C:\> Get-AzureRMADGroup -SearchString "PattiFuller"
 
           DisplayName                    Type                           ObjectId
           -----------                    ----                           --------
-          Christine Koch Team                                           2f9d4375-cbf1-48e8-83c9-2a0be4cb33fb
+          PattiFuller                                                   2f9d4375-cbf1-48e8-83c9-2a0be4cb33fb
 
           PS C:\> New-AzureRmRoleAssignment -ObjectId 2f9d4375-cbf1-48e8-83c9-2a0be4cb33fb -RoleDefinitionName Contributor  -ResourceGroupName rg1
 ```
 
-Grant access to a security group
+This command grants access to a security group.
 
-### --------------------------  Example 3  --------------------------
+### Example 3: Grant access to a resource
 
 
 ```
 PS C:\> New-AzureRmRoleAssignment -SignInName john.doe@contoso.com -RoleDefinitionName Owner -Scope "/subscription/86f81fc3-b00f-48cd-8218-3879f51ff362/resourcegroups/rg1/providers/Microsoft.Web/sites/site1"
 ```
 
-Grant access to a user at a resource (website)
+This command grants access to a user at a website resource.
 
-### --------------------------  Example 4  --------------------------
+### Example 4: Grant access to a nested resource
 
 
 ```
 PS C:\> New-AzureRMRoleAssignment -ObjectId 5ac84765-1c8c-4994-94b2-629461bd191b -RoleDefinitionName "Virtual Machine Contributor" -ResourceName Devices-Engineering-ProjectRND -ResourceType Microsoft.Network/virtualNetworks/subnets -ParentResource virtualNetworks/VNET-EASTUS-01 -ResourceGroupName Network
 ```
 
-Grant access to a group at a nested resource (subnet)
+This command grants access to a group at a nested subnet resource.
 
 ## PARAMETERS
 
 ### -ObjectId
-Azure AD Objectid of the user, group or service principal.
+Specifies an Azure Active Directory object ID of the user, group or service principal.
 
 ```yaml
 Type: Guid
@@ -166,10 +167,11 @@ Accept wildcard characters: False
 ```
 
 ### -Scope
-The Scope of the role assignment.
+Specifies the scope of the role assignment.
 In the format of relative URI.
-For e.g.
+For instance,
 "/subscriptions/9004a9fd-d58e-48dc-aeb2-4a4aec58606f/resourceGroups/TestRG".
+
 If not specified, will create the role assignment at subscription level.
 If specified, it should start with "/subscriptions/{id}".
 
@@ -198,8 +200,8 @@ Accept wildcard characters: False
 ```
 
 ### -RoleDefinitionName
-Name of the RBAC role that needs to be assigned to the principal i.e.
-Reader, Contributor, Virtual Network Administrator, etc.
+Specifies the name of the RBAC role that needs to be assigned to the principal.
+For instance: Reader, Contributor, Virtual Network Administrator.
 
 ```yaml
 Type: String
@@ -253,9 +255,9 @@ Accept wildcard characters: False
 ```
 
 ### -ResourceGroupName
-The resource group name.
+Specifies the name of the resource group.
 Creates an assignment that is effective at the specified resource group.
-When used in conjunction with ResourceName, ResourceType and (optionally)ParentResource parameters, the command constructs a hierarchical scope in the form of a relative URI that identifies a resource.
+When used in conjunction with the *ResourceName*, *ResourceType*, and *ParentResource* parameters, the command constructs a hierarchical scope in the form of a relative URI that identifies a resource.
 
 ```yaml
 Type: String
@@ -270,10 +272,9 @@ Accept wildcard characters: False
 ```
 
 ### -ResourceName
-The resource name.
-For e.g.
-storageaccountprod.
-Should only be used in conjunction with ResourceGroupName, ResourceType and (optionally)ParentResource parameters to construct a hierarchical scope in the form of a  relative URI that identifies a resource.
+Specifies the name of the resource.
+
+This parameter should only be used in conjunction with the *ResourceGroupName*, *ResourceType*, and *ParentResource* parameters to construct a hierarchical scope in the form of a relative URI that identifies a resource.
 
 ```yaml
 Type: String
@@ -288,10 +289,9 @@ Accept wildcard characters: False
 ```
 
 ### -ResourceType
-The resource type.
-For e.g.
-Microsoft.Network/virtualNetworks.
-Should only be used in conjunction with ResourceGroupName, ResourceName and (optionally)ParentResource parameters to construct a hierarchical scope in  the form of a relative URI that identifies a resource.
+Specifies the resource type.
+
+This parameter should only be used in conjunction with the *ResourceGroupName*, *ResourceName*, and *ParentResource* parameters to construct a hierarchical scope in the form of a relative URI that identifies a resource.
 
 ```yaml
 Type: String
@@ -306,8 +306,8 @@ Accept wildcard characters: False
 ```
 
 ### -ParentResource
-The parent resource in the hierarchy(of the resource specified using ResourceName parameter).
-Should only be  used in conjunction with ResourceGroupName, ResourceType and ResourceName parameters to construct a hierarchical scope in the form of a relative URI that identifies a resource.
+Specifies the parent resource in the hierarchy (of the resource specified using the *ResourceName* parameter).
+This parameter should only be used in conjunction with the *ResourceGroupName*, *ResourceType*, and *ResourceName* parameters to construct a hierarchical scope in the form of a relative URI that identifies a resource.
 
 ```yaml
 Type: String
@@ -322,7 +322,7 @@ Accept wildcard characters: False
 ```
 
 ### -RoleDefinitionId
-Id of the RBAC role that needs to be assigned to the principal.
+Specifies the ID of the RBAC role that needs to be assigned to the principal.
 
 ```yaml
 Type: Guid
@@ -337,7 +337,7 @@ Accept wildcard characters: False
 ```
 
 ### -SignInName
-The email address or the user principal name of the user.
+Specifies the email address or the user principal name of the user.
 
 ```yaml
 Type: String
@@ -352,7 +352,7 @@ Accept wildcard characters: False
 ```
 
 ### -ServicePrincipalName
-The ServicePrincipalName of the Azure AD application
+Specifies the ServicePrincipalName of the Azure Active Directory application.
 
 ```yaml
 Type: String
@@ -375,9 +375,8 @@ Keywords: azure, azurerm, arm, resource, management, manager, resource, group, t
 
 ## RELATED LINKS
 
-[Get-AzureRmRoleAssignment]()
-
-[Remove-AzureRmRoleAssignment]()
+[Get-AzureRmRoleAssignment](./Get-AzureRmRoleAssignment.md)
 
-[Get-AzureRmRoleDefinition]()
+[Remove-AzureRmRoleAssignment](./Remove-AzureRmRoleAssignment.md)
 
+[Get-AzureRmRoleDefinition](./Get-AzureRmRoleDefinition.md)

azureps-cmdlets-docs/ResourceManager/AzureRM.Resources/v3.7.0/New-AzureRmRoleDefinition.md

@@ -9,10 +9,7 @@ schema: 2.0.0
 
 ## SYNOPSIS
 Creates a custom role in Azure RBAC.
-Provide either a JSON role definition file or a PSRoleDefinition object as input.
-First, use the Get-AzureRmRoleDefinition command to generate a baseline role definition object.
-Then, modify its properties as required.
-Finally, use this command to create a custom role using role definition.
+
 
 ## SYNTAX
 
@@ -29,35 +26,35 @@ New-AzureRmRoleDefinition [-Role] <PSRoleDefinition> [-InformationAction <Action
 ```
 
 ## DESCRIPTION
-The New-AzureRmRoleDefinition cmdlet creates a custom role in Azure Role-Based Access Control.
-Provide a role definition as an input to the command as a JSON file or a PSRoleDefinition object.
+The **New-AzureRmRoleDefinition** cmdlet creates a custom role in Azure Role-Based Access Control.
+Provide a role definition as an input to the command as a JSON file or a **PSRoleDefinition** object.
 
 The input role definition MUST contain the following properties:
 
-1) DisplayName: the name of the custom role
+- DisplayName: the name of the custom role
 
-2) Description: a short description of the role that summarizes the access that the role grants.
+- Description: a short description of the role that summarizes the access that the role grants.
 
-3) Actions: the set of operations to which the custom role grants access.
+- Actions: the set of operations to which the custom role grants access.
 Use Get-AzureRmProviderOperations to get the operation for Azure resource providers that can be secured using Azure RBAC.
 Following are some valid operation strings:
  - "*/read" grants access to read operations of all Azure resource providers.
  - "Microsoft.Network/*/read" grants access to read operations for all resource types in the Microsoft.Network resource provider of Azure.
  - "Microsoft.Compute/virtualMachines/*" grants access to all operations of virtual machines and its child resource types.
 
-4) AssignableScopes: the set of scopes (Azure subscriptions or resource groups) in which the custom role will be available for assignment.
-Using AssignableScopes you can make the custom role available for assignment in only the subscriptions or resource groups that need it, and not clutter the user experience for the rest of the subscriptions or resource groups.
+- AssignableScopes: the set of scopes (Azure subscriptions or resource groups) in which the custom role will be available for assignment.
+Using the *AssignableScopes* parameter you can make the custom role available for assignment in only the subscriptions or resource groups that need it, and not clutter the user experience for the rest of the subscriptions or resource groups.
 Following are some valid assignable scopes:
  - "/subscriptions/c276fc76-9cd4-44c9-99a7-4fd71546436e", "/subscriptions/e91d47c4-76f3-4271-a796-21b4ecfe3624": makes the role available for assignment in two subscriptions.
  - "/subscriptions/c276fc76-9cd4-44c9-99a7-4fd71546436e": makes the role available for assignment in a single subscription.
  - "/subscriptions/c276fc76-9cd4-44c9-99a7-4fd71546436e/resourceGroups/Network": makes the role available for assignment only in the Network resource group.
 
 The input role definition MAY contain the following properties:
 
-1) NotActions: the set of operations that must be excluded from the Actions to determine the effective actions for the custom role.
+- NotActions: the set of operations that must be excluded from the Actions to determine the effective actions for the custom role.
 If there is a specific operation that you do not wish to grant access to in a custom role, it is convenient to use NotActions to exclude it, rather than specifying all operations other than that specific operation in Actions.
 
-NOTE: If a user is assigned a role that specifies an operation in NotActions and also assigned another role grants access to the same operation - the user will be able to perform that operation.
+If a user is assigned a role that specifies an operation in NotActions and also assigned another role grants access to the same operation - the user will be able to perform that operation.
 NotActions is not a deny rule - it is simply a convenient way to create a set of allowed operations when specific operations need to be excluded.
 
 Following is a sample json role definition that can be provided as input
@@ -79,36 +76,41 @@ Following is a sample json role definition that can be provided as input
         \],
         "AssignableScopes": \["/subscriptions/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx","/subscriptions/yyyyyyyy-yyyy-yyyy-yyyy-yyyyyyyyyyyy"\]
         }
+        
+You must provide either a JSON role definition file or a **PSRoleDefinition** object as input.
+First, use the [Get-AzureRmRoleDefinition](./Get-AzureRmRoleDefinition.md) command to generate a baseline role definition object.
+Then, modify its properties as required.
+Finally, use this command to create a custom role using role definition.
 
 ## EXAMPLES
 
-### --------------------------  Create using PSRoleDefinitionObject  --------------------------
+### Example 1:  Create a role definition file using PSRoleDefinitionObject
 
 
 ```
-PS C:\> $role = Get-AzureRmRoleDefinition -Name "Virtual Machine Contributor"
-          PS C:\> $role.Id = $null
-          PS C:\> $role.Name = "Virtual Machine Operator"
-          PS C:\> $role.Description = "Can monitor, start, and restart virtual machines."
-          PS C:\> $role.Actions.RemoveRange(0,$role.Actions.Count)
-          PS C:\> $role.Actions.Add("Microsoft.Compute/*/read")
-          PS C:\> $role.Actions.Add("Microsoft.Compute/virtualMachines/start/action")
-          PS C:\> $role.Actions.Add("Microsoft.Compute/virtualMachines/restart/action")
-          PS C:\> $role.Actions.Add("Microsoft.Compute/virtualMachines/downloadRemoteDesktopConnectionFile/action")
-          PS C:\> $role.Actions.Add("Microsoft.Network/*/read")
-          PS C:\> $role.Actions.Add("Microsoft.Storage/*/read")
-          PS C:\> $role.Actions.Add("Microsoft.Authorization/*/read")
-          PS C:\> $role.Actions.Add("Microsoft.Resources/subscriptions/resourceGroups/read")
-          PS C:\> $role.Actions.Add("Microsoft.Resources/subscriptions/resourceGroups/resources/read")
-          PS C:\> $role.Actions.Add("Microsoft.Insights/alertRules/*")
-          PS C:\> $role.Actions.Add("Microsoft.Support/*")
-          PS C:\> $role.AssignableScopes.Remove("/") | Out-Null
-          PS C:\> $role.AssignableScopes.Add("/subscriptions/c276fc76-9cd4-44c9-99a7-4fd71546436e")
-
-          PS C:\> New-AzureRmRoleDefinition -Role $role
+PS C:\> $Role = Get-AzureRmRoleDefinition -Name "Virtual Machine Contributor"
+          PS C:\> $Role.Id = $null
+          PS C:\> $Role.Name = "Virtual Machine Operator"
+          PS C:\> $Role.Description = "Can monitor, start, and restart virtual machines."
+          PS C:\> $Role.Actions.RemoveRange(0,$Role.Actions.Count)
+          PS C:\> $Role.Actions.Add("Microsoft.Compute/*/read")
+          PS C:\> $Role.Actions.Add("Microsoft.Compute/virtualMachines/start/action")
+          PS C:\> $Role.Actions.Add("Microsoft.Compute/virtualMachines/restart/action")
+          PS C:\> $Role.Actions.Add("Microsoft.Compute/virtualMachines/downloadRemoteDesktopConnectionFile/action")
+          PS C:\> $Role.Actions.Add("Microsoft.Network/*/read")
+          PS C:\> $Role.Actions.Add("Microsoft.Storage/*/read")
+          PS C:\> $Role.Actions.Add("Microsoft.Authorization/*/read")
+          PS C:\> $Role.Actions.Add("Microsoft.Resources/subscriptions/resourceGroups/read")
+          PS C:\> $Role.Actions.Add("Microsoft.Resources/subscriptions/resourceGroups/resources/read")
+          PS C:\> $Role.Actions.Add("Microsoft.Insights/alertRules/*")
+          PS C:\> $Role.Actions.Add("Microsoft.Support/*")
+          PS C:\> $Role.AssignableScopes.Remove("/") | Out-Null
+          PS C:\> $Role.AssignableScopes.Add("/subscriptions/c276fc76-9cd4-44c9-99a7-4fd71546436e")
+
+          PS C:\> New-AzureRmRoleDefinition -Role $Role
 ```
 
-### --------------------------  Create using JSON file  --------------------------
+### Example 2: Create a role definition using JSON file  
 
 
 ```
@@ -118,7 +120,7 @@ PS C:\> New-AzureRmRoleDefinition -InputFile C:\Temp\roleDefinition.json
 ## PARAMETERS
 
 ### -InputFile
-File name containing a single json role definition.
+File name containing a single JSON role definition.
 
 ```yaml
 Type: String
@@ -172,7 +174,7 @@ Accept wildcard characters: False
 ```
 
 ### -Role
-Role definition object.
+Specifies a role definition object.
 
 ```yaml
 Type: PSRoleDefinition
@@ -195,11 +197,10 @@ Keywords: azure, azurerm, arm, resource, management, manager, resource, group, t
 
 ## RELATED LINKS
 
-[Get-AzureRmProviderOperation]()
-
-[Get-AzureRmRoleDefinition]()
+[Get-AzureRmRoleDefinition](./Get-AzureRmRoleDefinition.md)
 
-[Set-AzureRmRoleDefinition]()
+[Remove-AzureRmRoleDefinition](./Remove-AzureRmRoleDefinition.md)
 
-[Remove-AzureRmRoleDefinition]()
+[Set-AzureRmRoleDefinition](./Set-AzureRmRoleDefinition.md)
 
+[Get-AzureRmProviderOperation](./Get-AzureRmProviderOperation.md)

azureps-cmdlets-docs/ResourceManager/AzureRM.Resources/v3.7.0/Register-AzureRmProviderFeature.md

@@ -22,11 +22,6 @@ The **Register-AzureRmProviderFeature** cmdlet registers an Azure provider featu
 
 ## EXAMPLES
 
-### 1:
-```
-
-```
-
 ## PARAMETERS
 
 ### -FeatureName
@@ -102,5 +97,3 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable
 ## RELATED LINKS
 
 [Get-AzureRmProviderFeature](./Get-AzureRmProviderFeature.md)
-
-