BlackBerry’s AtHoc crisis communication platform can now deliver real-time alerts directly into Microsoft Teams, leveraging Microsoft Entra ID for identity-based user provisioning and targeted notifications. The integration, announced on June 30, 2026, marks a significant step toward streamlining enterprise resilience by embedding critical alerting into the collaboration tools millions of workers already use daily.

For IT administrators and security teams, the combination addresses a long-standing friction point: getting urgent messages to the right people during emergencies, without requiring them to switch apps or maintain separate contact databases. Instead, AtHoc taps into the same identity fabric that governs access across the Microsoft ecosystem, ensuring that alerts reach employees based on their roles, locations, or other attributes stored in Entra ID.

What BlackBerry AtHoc Brings to the Table

AtHoc is a mission orchestration platform originally built for government and defense environments, where speed and reliability during crises are non-negotiable. It enables organizations to initiate alerts across multiple channels—sirens, desktop pop-ups, email, SMS, and now Teams—while providing real-time accountability through read receipts and response tracking. The system also supports two-way communication, allowing recipients to mark themselves safe, request assistance, or relay situational updates back to command centers.

Over the past decade, BlackBerry has expanded AtHoc beyond its military roots into commercial sectors, including healthcare, manufacturing, and education. The common thread is the need for a unified view of personnel safety during events ranging from severe weather and active shooter incidents to cybersecurity breaches and facility evacuations.

Seamless Integration with Microsoft Teams

With this integration, AtHoc becomes a native-feeling extension of the Teams environment. Organizations can configure AtHoc to send crisis notifications into specific Teams channels or directly to individual users via chat. The messages are not simple text pings; they can include rich, actionable content—such as interactive maps, embedded videos, or one-tap responses—that guide employees through an unfolding situation.

For example, during a fire, a facility manager might receive a Teams notification containing a floor plan with the fire’s location highlighted, along with a button to confirm evacuation. Simultaneously, all employees in the affected building get a Teams chat with clear instructions and a button to mark themselves safe. Because Teams is already part of many workers’ daily workflow, the alerts are less likely to be missed than an external app notification or an email buried in an inbox.

The integration also simplifies administration. Instead of manually importing and updating user lists, AtHoc synchronizes with the organization’s Microsoft Entra ID directory. When new employees are onboarded, they automatically inherit alerting rules tied to their department, office location, or other attributes. When someone leaves, their access revokes instantly, eliminating the risk of sending sensitive crisis information to ex-employees.

Microsoft Entra ID as the Identity Backbone

Entra ID (formerly Azure Active Directory) serves as the cloud-based identity and access management engine. By connecting AtHoc to Entra ID, BlackBerry enables what it calls “identity-driven crisis alerting.” This means alerting groups are dynamically maintained based on live directory data. If an employee changes roles or moves to a different office, their crisis notifications adjust automatically—no manual intervention needed.

This capability is critical for large enterprises with complex organizational structures. A multinational corporation, for instance, can instantly target all workers within a specific country during a regional emergency, without needing a static distribution list that might be outdated. Security teams can also overlay conditional access policies: for example, requiring that crisis alerts be sent only to managed devices, or that certain high-severity alerts trigger additional authentication steps before viewing.

The integration also supports guest and external user scenarios, common in Teams. Organizations can extend crisis alerts to external partners or contractors by granting them limited Entra ID guest accounts, which AtHoc can then include in alerts as needed.

Enhancing Crisis Management Workflows

Beyond simple paging, the AtHoc-Teams integration enables sophisticated crisis workflows. Incident commanders can use AtHoc’s web interface or mobile app to trigger multi-step communication plans that unfold within Teams. For example:

  • Initial alert: A Teams notification goes to all employees in a building, instructing them to evacuate.
  • Roll-call response: Employees tap “Safe” in the Teams message; AtHoc aggregates the responses in real time and displays a list of unaccounted personnel.
  • Follow-up instructions: Once outside, employees receive a second Teams message with information about alternate work locations or transportation.

All interactions are logged for post-incident analysis and regulatory compliance. Because the entire flow operates through Entra ID, audit trails tie each action to a verified identity, reducing the chance of spoofing or false reports.

BlackBerry also touts the platform’s ability to reach users across devices, including phones, desktops, and IP phones—all while keeping Teams as the unified interface. That means a crisis manager can confirm an alert’s delivery status, see who has acknowledged it, and escalate to voice or video calls within Teams, all without leaving the command console.

Real-World Impact and Enterprise Adoption

For enterprises already invested in Microsoft 365, the integration eliminates redundant infrastructure. There is no need to deploy a separate mobile app or train employees on a new tool; crisis alerts arrive where people already collaborate. This dramatically reduces the time to implement AtHoc and increases user adoption—both critical when seconds count.

Early adopters in the energy and healthcare sectors report that the integrated system reduces alert fatigue by tailoring messages to specific audiences. Instead of blanket notifications that desensitize staff, AtHoc plus Teams delivers only relevant alerts, increasing the likelihood that recipients will act promptly. In one hospital network, administrators used the integration to send targeted Teams alerts to nurses on specific floors during a hazmat incident, avoiding disruption to other departments.

Security and Compliance Considerations

BlackBerry emphasizes that the integration does not compromise security. All data in transit is encrypted end-to-end, and AtHoc inherits the same compliance certifications it has always held for government use, including FedRAMP and HIPAA. The tie-in with Entra ID adds an extra layer of access control: organizations can enforce multi-factor authentication (MFA) for users who need to acknowledge or respond to high-severity alerts, ensuring that only authorized personnel can take critical actions.

From a compliance standpoint, the unified audit trail simplifies reporting. Every step—from alert generation to user acknowledgment—is logged with Entra ID user identifiers, creating an immutable record suitable for regulatory review or internal investigations.

The Road Ahead

BlackBerry’s announcement positions AtHoc as a more open platform that can piggyback on enterprise investments in Microsoft infrastructure. Future updates may extend the integration to other Microsoft 365 services, such as SharePoint-based emergency templates or Power Automate workflows for automated incident response. Analysts note that as hybrid work persists, the need for location-agnostic crisis communication that follows the employee rather than the desk becomes paramount—and the Teams integration directly addresses that shift.

BlackBerry has confirmed that the Teams and Entra ID integrations are available immediately to all AtHoc customers with current licenses, with no additional cost. IT administrators can enable the feature through the AtHoc administrative console by linking their Entra ID tenant and configuring Teams notification channels.

Bottom Line for Windows-Centric Enterprises

For organizations standardized on Windows and Microsoft 365, the AtHoc integration closes a critical gap: the ability to push live-saving notifications into the same digital workspace where employees spend their day. It transforms Teams from a collaboration hub into a true safety hub, all while leveraging the identity governance that IT teams already trust. As crisis scenarios become more complex and distributed, such tight technology coupling may well become a baseline requirement rather than a luxury.