Design your service estate

Partition your estate by workload and tailor partner responsibilities with Trustmarque CloudTeaming Services.

Many organisations operate a range of workloads in cloud environments. Trustmarque’s CloudTeaming Services allow you to optimise investment in your portfolio of workloads by sharing management responsibility as part of a service agreement.

How can I design my estate for service?

The following example depicts a typical customer estate comprising 8 subscriptions, all of which are associated with a single Azure AD tenant. Each subscription hosts a specific workload.

Three of the subscriptions model a typical cross-subscription IaaS networking model in which a “Hub” subscription (perhaps providing on-premise connectivity and shared services such as Domain Controllers) is peered with two “Spoke” subscriptions with separate workloads.

Eight boxes representing subscriptions inside a single tenant box where some subscriptions are associated with service icons

Partitioning an IT estate by workload allows the type and extent of service to be assigned on a per-workload basis. In this example each workload is also partitioned into its own subscription. While it is fairly typical to partition organisational regimes by subscription, it is also possible to do this at both a less granular level (e.g. management groups) and a more granular level (e.g. resource groups).

Trustmarque recommend partitioning at a subscription level where possible. This tends to have the simplest management experience, broadest tooling support, and is easy to articulate to stakeholders.

Billing models

Our services support both CSP and Enterprise Agreement (EA) billing models. We recommend CSP for new services and subscriptions as we're able to support your organisation across the full procurement lifecycle, but our services are also available to customers purchasing Azure via an EA.

What factors drive service level?

Illustrating the output of a fictional decision process helps to understand how an organisation might make decisions about workloads and service levels. In our example:

  • Advice and Guidance for everything

    The Pro-Connect service has been applied to all subscriptions. In regular service meetings the health, goals, technologies, and security of each subscription is assessed. Staff responsible for these subscriptions are able to call Trustmarque for advice and guidance around provisioning and managing workloads and technologies.

    This offers a robust knowledge “safety net” for internal staff, a second pair of eyes to review roadmap, and timely, contextual improvement nudges.

  • Monitoring for a Legacy Application

    The Active Management (Co-managed) service has been applied to a spoke subscription, providing enhanced monitoring and alerting for a legacy application workload. Perhaps this application is old and temperamental. Trustmarque’s service works to detect failure states and triage the underlying issues, improving service delivery by supporting existing IT capability.

  • Infrastructure management for BI

    The Active Management (Fully-managed) service takes on all provisioning responsibility. In this case, perhaps it allows a BI team to utilise tooling without worrying about the underlying infrastructure which is monitored, patched, and maintained by Trustmarque.

  • Business-as-usual Apps

    The App Hosting service enables two applications to be run and managed entirely by Trustmarque. These may be stable line-of-business applications with a range of standard health metrics and service activities. They are effectively provided back to the organisation as SaaS applications for a predictable sum, enabling organisational IT teams to focus valuable delivery activities elsewhere.

  • Internal focus workloads

    Whether an organisation is delivering in-house innovation or tailoring IT with specialist domain processes, there will often be some parts of an estate that internal teams wish to control and manage themselves. In this case, development and test environments, and Application B. The latter is perhaps a new line-of-business app being customised to reflect organisational processes where full control is required by the IT team.

By designing for service, this organisation has effectively enabled their IT team to focus effort on priority business systems while retaining the right level of control over a broad IT estate which they may otherwise struggle to manage effectively.

Why design for service?

Designing your estate for service allows you to easily delegate “non-core” IT management activities to a third-party. This helps to keep in-house staff focused on delivering organisational value, utilising third-party service providers to support a broader IT estate than your team could ordinarily manage.

Third-party service providers benefit from an economy of scale which benefits both customer and provider, including:

  • Close vendor partnerships
  • Broad and deep experience leading to learning, improvement, and reduced risk
  • Access to trained, specialist resource often with niche expertise
  • Processes designed to simplify and define task scope, delivering high-value interactions

It can be difficult to both develop and maintain the practises, resources, and staff outside a service organisation where technology and situation exposure are typically greater.

With a sliding scale for responsibility transfer alongside flexibility to change this on a per-workload basis (enabled by our open Cloudmarque framework), we believe Trustmarque offers a compelling set of managed services to benefit your organisation.

Ready to speak to someone?

Our team is available to discuss your requirements and identify the services which best fit your needs. When you're ready to find out more, head over to our contact page to arrange a meeting with a consultant.