The situation
The group’s engineering and plant IT teams were provisioning infrastructure in AWS, Azure and a private VMware estate through whichever console or script each team knew. There was no shared catalog, approvals happened in email or not at all, tagging was inconsistent, and finance could not say what a project’s cloud footprint cost until the invoice arrived.
The ServiceNow platform was already in use for ITSM, which made it the obvious place to put cloud governance.
What we did
We deployed ITOM Visibility to discover the existing estate across all three clouds and populate the CMDB with the right relationships, then implemented IMGO, the Intelibliss Multi-cloud Governance and Orchestrator, our product of the time built on ServiceNow Cloud Provisioning and Governance:
- One portal with account, project and cloud-admin views, so each role saw its own resources, requests and spend.
- Provisioning catalogs for the standard workloads, with policy deciding what each project was allowed to request.
- Tag governance enforced at request time, with cost centre, owner and environment always present.
- Cost estimation from live AWS and Azure price books, shown before the request was submitted and before approval.
- Day 2 operations (resize, stop, start, decommission) through the same portal, with change records created automatically.
- Private cloud on VMware alongside public cloud, with the same catalog experience.
What changed
The group now provisions through one pane of glass for private and public cloud. Every resource in the CMDB has an owner and a cost centre, and finance sees estimated cost at request time rather than at invoice time. The client’s architect described the result as end-to-end multi-cloud governance with streamlined provisioning and stronger operational oversight.
IMGO was later published on the ServiceNow Store. Its successor, OneCloud, does the same job without depending on Cloud Provisioning and Governance, which ServiceNow has since marked for deprecation.
