Multihoming enables customer-side Nimbus administrators to distribute Microsoft Tenants across multiple Luware Clusters. This means a customer can initially create a tenant in any cluster and once established, enable the multihoming feature to create additional tenants in other clusters.
🤔 Why to consider this?
Multihoming allows you to maintain several tenants in different clusters, each configured with its own privacy settings and data storage locations. This can help you meet specific regulatory requirements applicable to you in each country the cluster is located, without sacrificing security or performance.
Data protection and compliance regulations can differ across countries, which can necessitate higher security standards. For example: When deploying a tenant in Switzerland that encompasses a German branch, it is common practice for customers to apply Germany’s stricter settings to the entire tenant to ensure uniform compliance. The Multihoming feature can support customers in their challenge of addressing diverse data protection and compliance regulations across multiple regions.
Multihoming Notes to consider:
When a tenant is spread over multiple Nimbus clusters, the following rules apply:
- Unique Users can be added only to one cluster at a time. The UI e.g. the User Administration will prevent access to the same user if was already added on another cluster.
- User / Service UPNs needs to be unique across all clusters. You can however use the same display name in the General Service Settings to make it appear consistent for customers (e.g. visiting your service on a website).
- Multi-homed tenants are marked in the Nimbus Admin UI. Administrative access levels can still be steered per Tenant (e.g. different Partner / Tenant Admins per cluster).
- This feature is not intended as a failover solution, but can be used as a “follow-the-sun” concept, e.g. once cluster dynamically taking over customers from the previous one as working shifts overlap. Also refer to Best Practices - Multihoming for further implementation considerations.
- Reporting data is completely separated between clusters, also meaning that details such as user state reporting can differ.
☝ Once the same tenant data exists on multiple clusters, the multihoming toggle cannot be switched off immediately. Reverting a already multi-homed to a single-homed tenant incorporates manual (services, users, resources, settings) deletion effort on the Nimbus tenant. Only afterwards Customer Success can revert the option which will impact the Nimbus UI on the remaining tenant accordingly.
Getting started
Adding tenants to multiple clusters requires Customer Success involvement as global Provisioning Tenant Settings need to be changed.
- Multihoming is a feature which is included in your License model. However, the onboarding must be specifically ordered from Customer Success.
- From a process perspective, once the initial tenant is created, the customer needs to submit an order to Luware. This is necessary due to legal requirements and the tenant opting in to potentially synchronize data across (potentially multiple) regions.
- The Luware Customer Success specialist will review the request, provide an Amendment to the Luware Cloud Services Terms of Use, and discuss the next steps.
- The Amendment to the Luware Cloud Services Terms of Use is to be signed by authorized signatories of the customer, in order to proceed with enabling multihoming. This ensures that all necessary agreements are in place for a smooth and compliant implementation.