Service Gaps

 

Applies To: System Center 2016 - Service Provider Foundation, System Center Technical Preview

Windows Azure Pack for Windows Server and API uses Service Provider Foundation to manage tenants and Virtual Machine Manager (VMM). However, the implementation of Service Provider Foundation includes some process edge-cases that you have to address with your own solutions. This topic describes each of these integration gap scenarios.

Plan updates

When a plan is changed in Windows Azure Pack for Windows Server and API, existing user roles are not updated with the changes. New user roles that are created after the changes are made are updated.

Note

This behavior does not apply to Service Provider Foundation for System Center 2012 R2.

Suspending or resuming subscriptions

When a subscription is suspended or resumed, the tenant object state is also changed accordingly. This state denies access to VMM through Service Provider Foundation. However, the tenant object state is opaque to VMM and continues to function. You must enable and disable all resources in VMM to which the tenant object has access. For example, VMM does not suspend or disable an assigned virtual machine when the tenant object is suspended.

Subscriptions with an active user role cannot be deleted

If a user role has access to objects in VMM, the subscription with which the user role is associated cannot be deleted. The user role must first be cleared of all associated objects, and then the subscription can be deleted.

See Also

Architecture Overview
Administration Database
OData Protocol
Service Provider Foundation Services