status

Author: meganbradley

articles/devtest-labs/add-artifact-repository.md

@@ -220,7 +220,7 @@ Personal access token for the GitHub or Azure Repos repository.
 Whether the artifact repository is a VSOGit (Azure Repos) or GitHub repository.
 
 .EXAMPLE
-Set-AzContext -SubscriptionId 11111111-1111-1111-1111-111111111111
+Set-AzContext -SubscriptionId aaaa0a0a-bb1b-cc2c-dd3d-eeeeee4e4e4e
 .\New-DevTestLabArtifactRepository.ps1 -LabName "mydevtestlab" -LabResourceGroupName "mydtlrg" -ArtifactRepositoryName "MyTeam Repository" -RepositoryUri "https://github.com/<myteam>/<nameofrepo>.git" -PersonalAccessToken "1111...." -SourceType "GitHub"
 
 .NOTES

articles/devtest-labs/automate-add-lab-user.md

@@ -139,7 +139,7 @@ First, create a parameter file (for example: azuredeploy.parameters.json) that p
   "contentVersion": "1.0.0.0",
   "parameters": {
     "principalId": {
-      "value": "11111111-1111-1111-1111-111111111111"
+      "value": "aaaaaaaa-bbbb-cccc-1111-222222222222"
     },
     "labName": {
       "value": "MyLab"
@@ -163,7 +163,7 @@ New-AzureRmResourceGroupDeployment -Name "MyLabResourceGroup-$(New-Guid)" -Resou
 If you plan to use the template several times to add several Active Directory objects to the DevTest Labs User role for your lab, consider using dynamic objects in your PowerShell command. The following example uses the [New-Guid](/powershell/module/Microsoft.PowerShell.Utility/New-Guid) cmdlet to specify the resource group deployment name and role assignment GUID dynamically.
 
 ```powershell
-New-AzureRmResourceGroupDeployment -Name "MyLabResourceGroup-$(New-Guid)" -ResourceGroupName 'MyLabResourceGroup' -TemplateFile .\azuredeploy.json -roleAssignmentGuid "$(New-Guid)" -labName "MyLab" -principalId "11111111-1111-1111-1111-111111111111"
+New-AzureRmResourceGroupDeployment -Name "MyLabResourceGroup-$(New-Guid)" -ResourceGroupName 'MyLabResourceGroup' -TemplateFile .\azuredeploy.json -roleAssignmentGuid "$(New-Guid)" -labName "MyLab" -principalId "aaaaaaaa-bbbb-cccc-1111-222222222222"
 ```
 
 ## Use Azure PowerShell

articles/devtest-labs/configure-shared-image-gallery.md

@@ -124,7 +124,7 @@ You can use an ARM template to attach a shared image gallery to your lab. You ne
         "name":"myGallery",
         "type":"sharedGalleries",
         "properties": {
-            "galleryId":"/subscriptions/11111111-1111-1111-1111-111111111111/resourceGroups/mySharedGalleryRg/providers/Microsoft.Compute/galleries/mySharedGallery",
+            "galleryId":"/subscriptions/aaaa0a0a-bb1b-cc2c-dd3d-eeeeee4e4e4e/resourceGroups/mySharedGalleryRg/providers/Microsoft.Compute/galleries/mySharedGallery",
             "allowAllImages": "Enabled"
         }
     }

articles/devtest-labs/devtest-lab-grant-user-permissions-to-specific-lab-policies.md

@@ -53,20 +53,20 @@ $policyRoleDef = (New-AzRoleDefinition -Role $policyRoleDef)
 ## Assigning permissions to a user for a specific policy using custom roles
 Once you’ve defined your custom roles, you can assign them to users. In order to assign a custom role to a user, you must first obtain the **ObjectId** representing that user. To do that, use the **Get-AzADUser** cmdlet.
 
-In the following example, the **ObjectId** of the *SomeUser* user is 05DEFF7B-0AC3-4ABF-B74D-6A72CD5BF3F3.
+In the following example, the **ObjectId** of the *SomeUser* user is aaaaaaaa-0000-1111-2222-bbbbbbbbbbbb.
 
 ```azurepowershell
 PS C:\>Get-AzADUser -SearchString "SomeUser"
 
 DisplayName                    Type                           ObjectId
 -----------                    ----                           --------
-[email protected]                                          05DEFF7B-0AC3-4ABF-B74D-6A72CD5BF3F3
+[email protected]                                          aaaaaaaa-0000-1111-2222-bbbbbbbbbbbb
 ```
 
 Once you have the **ObjectId** for the user and a custom role name, you can assign that role to the user with the **New-AzRoleAssignment** cmdlet:
 
 ```azurepowershell
-PS C:\>New-AzRoleAssignment -ObjectId 05DEFF7B-0AC3-4ABF-B74D-6A72CD5BF3F3 -RoleDefinitionName "Policy Contributor" -Scope /subscriptions/<SubscriptionID>/resourceGroups/<ResourceGroupName>/providers/Microsoft.DevTestLab/labs/<LabName>/policySets/default/policies/AllowedVmSizesInLab
+PS C:\>New-AzRoleAssignment -ObjectId aaaaaaaa-0000-1111-2222-bbbbbbbbbbbb -RoleDefinitionName "Policy Contributor" -Scope /subscriptions/<SubscriptionID>/resourceGroups/<ResourceGroupName>/providers/Microsoft.DevTestLab/labs/<LabName>/policySets/default/policies/AllowedVmSizesInLab
 ```
 
 In the previous example, the **AllowedVmSizesInLab** policy is used. You can use any of the following policies: