Service Deletion
Deleting an IZO™+ Multi Cloud Connect connection is a termination raised against an Active service in TCx. The single most important step is the cloud-side cleanup: terminating in TCx does not delete the hosted connection, virtual circuit or gateway in your cloud provider’s console, so you must remove those yourself or the cloud provider may keep charging you.
[Prerequisites] The connection must be Active to be terminated. Confirm no dependent components or downstream services still rely on it, and that any traffic has been moved off, before you begin.
Before you delete: pre-deletion checks
Decommissioning is deliberate. Before raising a termination:
-
Confirm the connection is no longer carrying production traffic, using the monitoring dashboards.
-
Check inventory for dependent components: a shared routing element or a cloud interconnect that other connections rely on should not be removed while they are in use.
-
Note the cloud-side objects that will need to be deleted afterwards (hosted connection or virtual circuit, gateway, and any related routing).
Raising the termination
Termination is placed against the Active service. Once submitted, the connection moves to Termination In Progress and then to Terminated when it completes. If the termination automation does not complete, the state shows Termination API Failure and the Tata Communications backend team completes the termination manually, after which the connection reaches Terminated. For the full state set, see Connection Lifecycle.
What’s on the cloud side
The cloud connection at the far end is created, and must be deleted, in the cloud provider’s console. Terminating the connection in TCx removes the Tata Communications side and stops Tata Communications billing, but the hosted connection or virtual circuit, the gateway and any associated routing remain in your cloud account until you delete them. Remove them promptly to avoid continued cloud-provider charges; for the cloud-side deletion steps and routing, see the relevant per-cloud section.
Final billing reconciliation
Terminating a connection stops its recurring charge on the Tata Communications side from the point of termination. Review the next invoice in the Billing & Invoice module to confirm the charge has ceased, and raise a Billing Ticket if anything needs to be queried (see Billing and Invoices). Remember that any cloud-provider charges for objects left in place are billed by the cloud provider, not by Tata Communications.