OpenText Webroot Unity - Microsoft Dynamics Integration and Automation

Common Integration Use Cases Between OpenText Webroot Unity and Microsoft Dynamics

• Customer and account risk enrichment for sales and service teams
  OpenText Webroot Unity can send device and threat intelligence into Microsoft Dynamics to enrich customer, account, or contact records with security risk indicators. Sales and service teams gain visibility into whether a customer environment is experiencing malware, phishing, or ransomware activity, helping them prioritize outreach, adjust engagement, and coordinate with security stakeholders.
• Security incident case creation from endpoint alerts
  When OpenText Webroot Unity detects a high severity threat on a managed endpoint, it can create a case or incident in Microsoft Dynamics for follow up by customer support, managed services, or internal IT teams. This improves response coordination, ensures accountability, and gives business teams a single place to track remediation status, owner, and customer communications.
• Automated service ticket updates with endpoint remediation status
  Microsoft Dynamics service records can be updated bi directionally with remediation details from OpenText Webroot Unity, such as threat type, affected device, containment status, and resolution time. Support teams no longer need to manually check the security console, which reduces handling time and improves case closure accuracy.
• Customer onboarding and security posture validation
  During customer onboarding or account setup in Microsoft Dynamics, integration can verify whether required endpoint protection policies are deployed through OpenText Webroot Unity. If devices are missing protection or are not compliant, Dynamics can trigger onboarding tasks, escalation workflows, or customer notifications before the account is fully activated.
• Renewal and retention prioritization based on security exposure
  Microsoft Dynamics can use threat and compliance data from OpenText Webroot Unity to flag accounts with elevated security exposure, repeated incidents, or unmanaged devices. Account managers can use this information to prioritize renewal conversations, recommend additional security services, and reduce churn risk by addressing operational concerns early.
• Incident driven customer communications workflow
  When OpenText Webroot Unity identifies a significant threat event, Microsoft Dynamics can automatically generate customer communication tasks, email templates, or follow up activities for account teams. This ensures timely, consistent communication with affected customers and reduces the chance of missed notifications during security incidents.
• Operational reporting across security and business functions
  Security event data from OpenText Webroot Unity can be synchronized into Microsoft Dynamics reporting structures to correlate endpoint threats with customer segments, service tiers, regions, or support volumes. Leadership can use this combined view to identify patterns, measure incident impact on service operations, and improve resource planning.
• Managed security service delivery tracking
  For organizations delivering security services to customers, OpenText Webroot Unity can feed protection status and incident data into Microsoft Dynamics to support SLA tracking, service reviews, and billing related workflows. This gives service delivery, finance, and account teams a shared operational record of what was protected, when incidents occurred, and how quickly they were resolved.