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/app-provisioning/use-scim-to-build-users-and-groups-endpoints.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
@@ -99,7 +99,7 @@ The default token validation code is configured to use an Azure AD token and req
99
99
100
100
After you deploy the SCIM endpoint, you can test to ensure that it's compliant with SCIM RFC. This example provides a set of tests in Postman that validate CRUD (create, read, update, and delete) operations on users and groups, filtering, updates to group membership, and disabling users.
101
101
102
-
The endpoints are in the `{host}/scim/` directory, and you can use standard HTTP requests to interact with them. To modify the `/scim/` route, see *ControllerConstant.cs* in **AzureADProvisioningSCIMreference** > **ScimReferenceApi** > **Controllers**.
102
+
The endpoints are in the `{host}/scim/` directory, and you can use standard HTTP requests to interact with them. To modify the `/scim/` route, see *TokenController.cs* in **SCIMReferenceCode** > **Microsoft.SCIM.WebHostSample** > **Controllers**.
103
103
104
104
> [!NOTE]
105
105
> You can only use HTTP endpoints for local tests. The Azure AD provisioning service requires that your endpoint support HTTPS.
@@ -141,4 +141,4 @@ To develop a SCIM-compliant user and group endpoint with interoperability for a
141
141
142
142
> [!div class="nextstepaction"]
143
143
> [Tutorial: Develop and plan provisioning for a SCIM endpoint](use-scim-to-provision-users-and-groups.md)
144
-
> [Tutorial: Configure provisioning for a gallery app](configure-automatic-user-provisioning-portal.md)
144
+
> [Tutorial: Configure provisioning for a gallery app](configure-automatic-user-provisioning-portal.md)
<sup>1</sup> Depending on category/subcategory and industry selection.<br>
54
52
<sup>2</sup> Offers with private plans will be published to the Azure portal.<br>
@@ -89,8 +87,7 @@ Industry selection applies only for offers published to AppSource and Consulting
89
87
| Media and Communications | Media and Entertainment<br>Telecommunications |
90
88
| Professional Services | Partner Professional Services<br>Legal<br>Architecture and Construction<br>Real Estate |
91
89
| Distribution | Wholesale<br>Parcel and Package Shipping |
92
-
| Hospitality and Travel | Travel & Transportation<br>Hotels and Leisure<br>Restaurants and Food Services |
93
-
|
90
+
| Hospitality and Travel | Travel & Transportation<br>Hotels and Leisure<br>Restaurants and Food Services |
94
91
95
92
## Applicable products
96
93
@@ -99,4 +96,4 @@ Select the applicable products your app works with for the offer to show up unde
99
96
## Next steps
100
97
101
98
- To create an offer, sign in to [Partner Center](https://go.microsoft.com/fwlink/?linkid=2165290) to create and configure your offer. If you haven't yet enrolled in Partner Center, [create an account](./create-account.md).
102
-
- For step-by-step instructions on publishing an offer, see the commercial marketplace [publishing guide by offer type](./publisher-guide-by-offer-type.md).
99
+
- For step-by-step instructions on publishing an offer, see the commercial marketplace [publishing guide by offer type](./publisher-guide-by-offer-type.md).
- Spreading aligned with storage disk fault domains (platformFaultDomainCount = 2 or 3)
@@ -43,7 +44,7 @@ When you deploy a scale set, you also have the option to deploy with a single [p
43
44
44
45
Finally, for scale sets deployed across multiple zones, you also have the option of choosing "best effort zone balance" or "strict zone balance". A scale set is considered "balanced" if each zone the same number of VMs or +\\- 1 VM in all other zones for the scale set. For example:
45
46
46
-
- A scale set with 2 VMs in zone 1, 3 VMs in zone 2, and 3 VMs in zone 3 is considered balanced. There is only one zone with a different VM count and it is only 1 less than the other zones.
47
+
- A scale set with 2 VMs in zone 1, 3 VMs in zone 2, and 3 VMs in zone 3 is considered balanced. There is only one zone with a different VM count and it is only 1 less than the other zones.
47
48
- A scale set with 1 VM in zone 1, 3 VMs in zone 2, and 3 VMs in zone 3 is considered unbalanced. Zone 1 has 2 fewer VMs than zones 2 and 3.
48
49
49
50
It's possible that VMs in the scale set are successfully created, but extensions on those VMs fail to deploy. These VMs with extension failures are still counted when determining if a scale set is balanced. For instance, a scale set with 3 VMs in zone 1, 3 VMs in zone 2, and 3 VMs in zone 3 is considered balanced even if all extensions failed in zone 1 and all extensions succeeded in zones 2 and 3.
@@ -64,7 +65,7 @@ When you create a scale set in a single zone, you control which zone all those V
64
65
To use Availability Zones, your scale set must be created in a [supported Azure region](../availability-zones/az-region.md). You can create a scale set that uses Availability Zones with one of the following methods:
@@ -80,7 +81,11 @@ The scale set and supporting resources, such as the Azure load balancer and publ
80
81
81
82
The process to create a scale set that uses an Availability Zone is the same as detailed in the [getting started article](quick-create-cli.md). To use Availability Zones, you must create your scale set in a supported Azure region.
82
83
83
-
Add the `--zones` parameter to the [az vmss create](/cli/azure/vmss) command and specify which zone to use (such as zone *1*, *2*, or *3*). The following example creates a single-zone scale set named *myScaleSet* in zone *1*:
84
+
Add the `--zones` parameter to the [az vmss create](/cli/azure/vmss) command and specify which zone to use (such as zone *1*, *2*, or *3*).
85
+
86
+
### Single-zone scale set
87
+
88
+
The following example creates a single-zone scale set named *myScaleSet* in zone *1*:
84
89
85
90
```azurecli
86
91
az vmss create \
@@ -93,7 +98,7 @@ az vmss create \
93
98
--zones 1
94
99
```
95
100
96
-
For a complete example of a single-zone scale set and network resources, see [this sample CLI script](https://github.com/Azure/azure-docs-cli-python-samples/blob/master/virtual-machine-scale-sets/create-single-availability-zone/create-single-availability-zone.sh)
101
+
For a complete example of a single-zone scale set and network resources, see [this sample CLI script](scripts/cli-sample-single-availability-zone-scale-set.md#sample-script)
97
102
98
103
### Zone-redundant scale set
99
104
@@ -112,12 +117,14 @@ az vmss create \
112
117
--zones 1 2 3
113
118
```
114
119
115
-
It takes a few minutes to create and configure all the scale set resources and VMs in the zone(s) that you specify. For a complete example of a zone-redundant scale set and network resources, see [this sample CLI script](https://github.com/Azure/azure-docs-cli-python-samples/blob/master/virtual-machine-scale-sets/create-zone-redundant-scale-set/create-zone-redundant-scale-set.sh)
120
+
It takes a few minutes to create and configure all the scale set resources and VMs in the zone(s) that you specify. For a complete example of a zone-redundant scale set and network resources, see [this sample CLI script](scripts/cli-sample-zone-redundant-scale-set.md#sample-script)
116
121
117
122
## Use Azure PowerShell
118
123
119
124
To use Availability Zones, you must create your scale set in a supported Azure region. Add the `-Zone` parameter to the [New-AzVmssConfig](/powershell/module/az.compute/new-azvmssconfig) command and specify which zone to use (such as zone *1*, *2*, or *3*).
120
125
126
+
### Single-zone scale set
127
+
121
128
The following example creates a single-zone scale set named *myScaleSet* in *East US 2* zone *1*. The Azure network resources for virtual network, public IP address, and load balancer are automatically created. When prompted, provide your own desired administrative credentials for the VM instances in the scale set:
122
129
123
130
```powershell
@@ -154,6 +161,8 @@ New-AzVmss `
154
161
155
162
The process to create a scale set that uses an Availability Zone is the same as detailed in the getting started article for [Linux](quick-create-template-linux.md) or [Windows](quick-create-template-windows.md). To use Availability Zones, you must create your scale set in a supported Azure region. Add the `zones` property to the *Microsoft.Compute/virtualMachineScaleSets* resource type in your template and specify which zone to use (such as zone *1*, *2*, or *3*).
156
163
164
+
### Single-zone scale set
165
+
157
166
The following example creates a Linux single-zone scale set named *myScaleSet* in *East US 2* zone *1*:
0 commit comments