Connect governance to your ticket system
AI summary
Connect your governance policies to the ticket systems and tools your team already uses through custom automations. When policies are violated, on schedule, or manually, automations can open ServiceNow tickets, start Power Automate flows, or post Teams notifications.
Track governance work in the tools your teams already use. An automation can send an HTTP request or trigger a webhook to open a ticket, start a Power Automate flow or post in Teams.
Applies to
Who it is for: IT operations and the owners of the ticket process.
Steps
- Pick the event. Read the available triggers for automations: manually, on schedule or on policy violationViolationA violation is an inventory object that matches the rule of an active policy, such as a Team with no owner.Read more.
- Open a ticket. Create ServiceNow tickets with the Send HTTP requestWebhookA webhook is a URL another system listens on, so that a call to it starts something there.Read more action. The same action works for other ticket systems that accept REST calls.
- Start your own flow. Trigger a webhook for Power Automate.
- Post to TeamsMicrosoft TeamsMicrosoft Teams is the Microsoft 365 app for chat, meetings and team collaboration.Read more. Configure a Teams notification.
- Run it after a review. Pick the automation in the review automations.
- If a run fails, see troubleshooting automation errors.
You build these with a custom automation. The examples above use the Users inventory, but any inventory objectInventory objectAn inventory object is one item Rencore Governance has scanned from a connector, such as a single Team, SharePoint site collection, user or Power App.Read more your policy reports works the same way.
Policy templates
Any policy can trigger the automation. Start with the policy templatesPolicyA policy is a governance rule that Rencore Governance checks against your inventory, for example Teams without owners.Read more of the services you govern, for example Teams policies, SharePoint policies and Microsoft 365 policies.
Limits
- Rencore Governance opens tickets. It does not comment on or close a ticket, and nothing syncs back.
- Authentication for HTTP requests is None, Basic or raw headers. OAuth sign-in is not available.
- Calls are sent in batches, about one to two minutes after the event.
- See What are the limitations of automations?.
Frequently asked questions
How do I create a ServiceNow ticket from a Rencore Governance automation?
Use the Send HTTP request action in a custom automation to create ServiceNow tickets. The same action also works for other ticket systems that accept REST calls.
Which authentication methods are available for HTTP requests in automations?
Authentication for HTTP requests can be None, Basic or raw headers. OAuth sign-in is not available.
Does Rencore Governance update or close tickets after it opens them?
No. Rencore Governance only opens tickets. It does not comment on or close a ticket, and nothing syncs back from the ticket system.
Was this page helpful?
Thanks for the feedback.
Thanks. What was wrong?