Actions & Integrations
Resource Lens connects recurring Azure savings reviews to the tools teams already use, while leaving every Azure change and external task under customer control.
Notify the right people
- Send concise completed, failed, blocked, awaiting-input, skipped, and report-ready notifications to Microsoft Teams Workflows or Slack incoming webhooks.
- Choose which schedules and event types reach each destination.
- Keep sensitive resource evidence and report details behind authenticated Resource Lens links.
- Retain durable delivery history with bounded retries and actionable connection errors.
Create reviewable engineering work
- Preview the title, estimated savings, risk, implementation guidance, and Resource Lens link before submission.
- Create a linked Azure DevOps Services work item, Jira Cloud issue, or GitHub issue only when an owner or analyst explicitly requests it.
- Select the destination project, repository, and supported task or issue type.
- Keep one durable external link per action and configured destination, with correlation markers that prevent blind duplicate creation.
Customer-controlled by design
Owners manage connections, destinations, notification events, tests, disablement, disconnection, and delivery history. OAuth credentials and webhook destinations are encrypted and never returned to the browser after storage.
External task status does not change Resource Lens action status or confirmed savings. Resource Lens does not offer chat approvals, automatic task creation, bidirectional synchronization, or any mechanism that modifies Azure resources.
Supported cloud services
- Microsoft Teams: analysis and report notifications through Teams Workflows webhooks.
- Slack: analysis and report notifications through incoming webhooks.
- Azure DevOps Services: explicit work-item creation through Microsoft Entra OAuth.
- Jira Cloud: explicit issue creation through OAuth authorization.
- GitHub: explicit issue creation through the public Resource Lens GitHub App.