| Excerpt | ||
|---|---|---|
| ||
A customer-managed tenant is a separate, isolated, regulated and governed deployment of our product within our clients perimeter. Clients that opt for this approach provide their own landing-zone that they can reach e.g. with There exist many variants of this model depending mostly on the distribution of the responsibilities between the client and Unique. |
...
| Table of Contents | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Get started
Learn how a customer managed tenant gets started from scratch.
Responsibilities
In Get started with a Customer Managed Tenant the responsibilities were defined. Independently from the who-does-who there are two key phases to the customer managed tenant model.
Setup phase, where the responsible parties sets up the landing zone, the resources within it and ultimately install
itselfRun phase, where the responsible parties run, maintain, investigate and operate
and potentially some resources
Since the https://unique-ch.atlassian.net/wiki/spaces/PUB/pages/434896928/Get+started+with+a+Customer+Managed+Tenant#Responsibilities are very flexible, it is difficult to outline these phases in detail but you find information about both phases in their respective pages linked above.
Architecture
The architecture, as everything, heavily depends on the responsibilities. Unique is either consulted if the client is responsible or Unique implements the setup if they are responsible.
...
|
...
Phases
When preparing, setting up and running a customer managed tenant, Unique identifies three main phases that are each documented in
...
Infrastructure Architecture
Unique can advice on a recommended architecture by effort
...
When responsible, Unique will self implement the recommended architecture
This , this recommended architecture is outlined in
...
Governance
...
Regarding the application architecture itself, please refer to
...
...
Author | See Parent |
|---|