Skip to content

Commit ff15506

Browse files
authored
Merge pull request #181581 from MicrosoftDocs/repo_sync_working_branch
Confirm merge from repo_sync_working_branch to master to sync with https://github.com/MicrosoftDocs/azure-docs (branch master)
2 parents 8ea908f + 35d927f commit ff15506

File tree

4 files changed

+24
-5
lines changed

4 files changed

+24
-5
lines changed

articles/active-directory/app-provisioning/use-scim-to-provision-users-and-groups.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -269,7 +269,7 @@ This section provides example SCIM requests emitted by the AAD SCIM client and e
269269

270270
### User Operations
271271

272-
* Users can be queried by `userName` or `email[type eq "work"]` attributes.
272+
* Users can be queried by `userName` or `emails[type eq "work"]` attributes.
273273

274274
#### Create User
275275

articles/active-directory/saas-apps/dome9arc-tutorial.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -167,8 +167,11 @@ In this section, you'll enable B.Simon to use Azure single sign-on by granting a
167167

168168
To enable Azure AD users to sign in to Check Point CloudGuard Posture Management, they must be provisioned into application. Check Point CloudGuard Posture Management supports just-in-time provisioning but for that to work properly, user have to select particular **Role** and assign the same to the user.
169169

170-
> [!Note]
171-
> For **Role** creation and other details contact [Check Point CloudGuard Posture Management Client support team](mailto:[email protected]).
170+
> [!NOTE]
171+
> To learn how to create a **Role** and for other information, see the [CloudGuard Admin Guide](https://sc1.checkpoint.com/documents/CloudGuard_Dome9/Documentation/Integrations/Single-Sign-On/SSO-ADFS.htm).
172+
>
173+
> For 24/7 assistance, contact [Check Point Support](https://www.checkpoint.com/support-services/contact-support/).
174+
>
172175
173176
**To provision a user account manually, perform the following steps:**
174177

articles/data-factory/tutorial-copy-data-dot-net.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,7 @@ If you don't have an Azure subscription, create a [free Azure account](https://a
3939

4040
### Create a blob and a SQL table
4141

42-
Now, prepare your Azure Blob and Azure SQL Database for the tutorial by creating a source blog and a sink SQL table.
42+
Now, prepare your Azure Blob and Azure SQL Database for the tutorial by creating a source blob and a sink SQL table.
4343

4444
#### Create a source blob
4545

articles/virtual-machine-scale-sets/virtual-machine-scale-sets-faq.yml

Lines changed: 17 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -473,8 +473,9 @@ sections:
473473
Update the admin credentials directly in the scale set model (for example using the Azure Resource Explorer, PowerShell or CLI). Once the scale set is updated, all new VMs have the new credentials. Existing VMs only have the new credentials if they are reimaged.
474474
475475
- Reset the password using the VM access extensions. Make sure to follow the password requirements as described [here](../virtual-machines/windows/faq.yml#what-are-the-password-requirements-when-creating-a-vm-).
476+
- Using a VM access extension doesn't require reimaging because the extension doesn't update the password in the model. The extension runs a script to append the password to the password or to the SSH key file. The extension doesn't remove the original SSH key.
476477
477-
Use the following PowerShell example:
478+
Use the following PowerShell example for a Windows virtual machine scale set:
478479
479480
```powershell
480481
$vmssName = "myvmss"
@@ -489,6 +490,21 @@ sections:
489490
Update-AzVmss -ResourceGroupName $vmssResourceGroup -Name $vmssName -VirtualMachineScaleSet $vmss
490491
```
491492
493+
Use the following PowerShell example for a Linux virtual machine scale set:
494+
495+
```powershell
496+
$vmssName = "myvmss"
497+
$vmssResourceGroup = "myvmssrg"
498+
$publicConfig = @{"UserName" = "newuser"}
499+
$privateConfig = @{"Password" = "********"}
500+
501+
$extName = "VMAccessForAgent"
502+
$publisher = "Microsoft.OSTCExtensions"
503+
$vmss = Get-AzVmss -ResourceGroupName $vmssResourceGroup -VMScaleSetName $vmssName
504+
$vmss = Add-AzVmssExtension -VirtualMachineScaleSet $vmss -Name $extName -Publisher $publisher -Setting $publicConfig -ProtectedSetting $privateConfig -Type $extName -TypeHandlerVersion "1.4" -AutoUpgradeMinorVersion $true
505+
Update-AzVmss -ResourceGroupName $vmssResourceGroup -Name $vmssName -VirtualMachineScaleSet $vmss
506+
```
507+
492508
- name: Networking
493509
questions:
494510
- question: |

0 commit comments

Comments
 (0)