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/virtual-machines/spot-placement-score.md
+4-8Lines changed: 4 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -74,7 +74,7 @@ Find the Spot Placement Score in the Spot tab of the Virtual Machine Scale Sets
74
74
75
75
### [REST API](#tab/rest-api)
76
76
77
-
Use the following REST API to get your Spot Placement Score. The Placement Score API supports the following versions: *2024-03-01-preview* and *2024-06-01-preview*.
77
+
Use the following REST API to get your Spot Placement Score. The Placement Score API supports the following versions: *2024-03-01-preview* and *2024-06-01-preview*. You will need to add the RBAC role "Compute Recommendations Role" and select the members to enable the subscription they want to run the API on (https://learn.microsoft.com/azure/role-based-access-control/role-assignments-portal).
78
78
79
79
```
80
80
POST https://management.azure.com/subscriptions/{subscription}/providers/Microsoft.Compute/locations/{region}/placementScores/spot/generate?api-version={api-version}
@@ -89,8 +89,9 @@ POST https://management.azure.com/subscriptions/{subscription}/providers/Microso
89
89
"desiredCount": ""
90
90
}
91
91
```
92
-
93
-
Restricted SKU Data Not Found
92
+
Some important terminology to consider:
93
+
**Restricted SKU** is returned if the Spot VM SKU is not available for the subscription.
94
+
**Data Not Found** is returned when the data necessary to generate a score or recommendation is either not found in upstream databases, or is found but the data lifespan is greater than what our service considers "fresh".
94
95
95
96
### [Azure CLI 2.0](#tab/cli)
96
97
@@ -127,11 +128,6 @@ Invoke-AzSpotPlacementScore
127
128
128
129
The following examples have scenario assumptions and a table with the results score to help you understand how Spot Placement Score works.
129
130
130
-
Some important terminology to notice before referring to these examples:
131
-
132
-
-**sku.capacity** is the total number of VMs in the Virtual Machine Scale Set
133
-
-**Base (standard) VMs** are the number of standard non-Spot VMs, akin to a minimum VM number
134
-
135
131
### Scenario 1
136
132
This is an example of a request returning regionally scoped placement scores for multiple desired VM sizes and regions.
0 commit comments