Requesting feature to select from/ target capacity reservation groups (not manage fall-back SKUs, not manage reservations) such that the build assigns the group during the build process and isn't relying on a custom script to target the group.
The base cause is that the feature/ setting is not exposed in the NMM console. Reserved Instance settings are all that are available, but do not account for Capacity Reservations. Would like to see this feature added to the build side of the host pool settings rather than requiring a scripted action.
Current resource constraints are causing failures during deployment to some SKUs. Customers have created Capacity Reservations to lock in those SKUs for availability, but the NMM deployment does not recognize the setting. Using Scripted Actions, we can add the machine late in the deployment cycle provided there are available hosts to kick off the deployment.
Manual action is sometimes available but appears sloppy to the customer.
Allowing selection as an advanced option will set the parameter during the host pool build and ensure the leased capacity group is utilized and put Microsoft under SLA to provide the resource pool on demand, regardless of other constraints in their zones.
Additionally, other advanced options are on my agenda, such as allowing log analytics workspace selection during the NMM configuration on the client subscription, selection of a pre-existing automation account, and selection of a pre-existing key vault (this one currently requires disabling security settings in the subscriptions to allow deployment - we have to then fix the key vault before re-enabling the policy).
Submitted on behalf of the MSP, Helient Systems.
Comments (0 comments)