Skip to content

Commit 399cffb

Browse files
authored
Merge pull request #206320 from MicrosoftDocs/repo_sync_working_branch
Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)
2 parents 70ea4ef + 2387df9 commit 399cffb

File tree

4 files changed

+14
-12
lines changed

4 files changed

+14
-12
lines changed

articles/active-directory-b2c/technicalprofiles.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -249,6 +249,7 @@ The **InputClaim** element contains the following attributes:
249249
| --------- | -------- | ----------- |
250250
| ClaimTypeReferenceId | Yes | The identifier of a claim type. The claim is already defined in the claims schema section in the policy file or parent policy file. |
251251
| DefaultValue | No | A default value to use to create a claim if the claim indicated by ClaimTypeReferenceId doesn't exist so that the resulting claim can be used as an InputClaim element by the technical profile. |
252+
|AlwaysUseDefaultValue |No |Forces the use of the default value. |
252253
| PartnerClaimType | No | The identifier of the claim type of the external partner that the specified policy claim type maps to. If the PartnerClaimType attribute isn't specified, the specified policy claim type is mapped to the partner claim type of the same name. Use this property when your claim type name is different from the other party. An example is if the first claim name is *givenName*, while the partner uses a claim named *first_name*. |
253254

254255
## Display claims

articles/center-sap-solutions/install-software.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -91,6 +91,7 @@ Before you can download the software, set up an Azure Storage account for the do
9191
- `wheel` version 0.37.1
9292
- `jq` version 1.6
9393
- `ansible` version 2.9.27
94+
- `netaddr` version 0.8.0
9495
- `zip`
9596
- `netaddr` version 0.8.0
9697

articles/iot-dps/quick-create-simulated-device-x509.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -169,7 +169,7 @@ In this section, you'll prepare a development environment that's used to build t
169169
170170
::: zone pivot="programming-language-python"
171171
172-
1. In your Windows command prompt, clone the [Azure IoT Samples for Python](https://github.com/Azure/azure-iot-sdk-node.git) GitHub repository using the following command:
172+
1. In your Windows command prompt, clone the [Azure IoT Samples for Python](https://github.com/Azure/azure-iot-sdk-python.git) GitHub repository using the following command:
173173
174174
```cmd
175175
git clone https://github.com/Azure/azure-iot-sdk-python.git --recursive

articles/virtual-machines/linux/run-command-managed.md

Lines changed: 11 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -180,18 +180,18 @@ To deploy scripts sequentially, use a deployment template, specifying a `depends
180180

181181
```json
182182
{
183-
"type":"Microsoft.Compute/virtualMachines/runCommands",
184-
"name":"secondRunCommand",
185-
"apiVersion":"2019-12-01",
186-
"location":"[parameters('location')]",
187-
"dependsOn":<full resourceID of the previous other Run Command>,
188-
"properties": {
189-
"source": { 
190-
"script":"echo Hello World!"
191-
},
192-
"timeoutInSeconds": 60 
183+
"type":"Microsoft.Compute/virtualMachines/runCommands",
184+
"name":"secondRunCommand",
185+
"apiVersion":"2019-12-01",
186+
"location":"[parameters('location')]",
187+
"dependsOn":<full resourceID of the previous other Run Command>,
188+
"properties":{
189+
"source":{
190+
"script":"echo Hello World!"
191+
},
192+
"timeoutInSeconds":60
193193
}
194-
}
194+
}
195195
```
196196

197197
### Execute multiple Run Commands sequentially

0 commit comments

Comments
 (0)