Revoking access
Delete the role. That is the whole procedure.
How
Delete the role, service principal, service account, token or API key you created for CoverOps. It takes effect immediately, because the permission lived in your account rather than ours.
What keeps running
Your infrastructure keeps running and your pipelines continue to deploy, because none of it ever ran on us. Nothing degrades because CoverOps stopped being able to reach it. See portability for why that is a design constraint rather than a courtesy.
Your records
Every change CoverOps made was an ordinary provider API call, already in your CloudTrail or Azure Activity Log. Export CoverOps' own audit log as JSON from Settings before you go if you want its side of the history too.
What the role could do while it existed is on the access model.