BlackBerry has released version 7.22 of its AtHoc Cloud critical event management (CEM) platform, introducing deeper ties with Microsoft’s identity and collaboration ecosystem. The update, which became generally available on June 30, 2026, adds direct synchronization with Microsoft Entra ID (formerly Azure Active Directory) and expands crisis collaboration capabilities within Microsoft Teams. For enterprise IT teams steeped in the Windows world, these enhancements transform AtHoc from a standalone emergency notification tool into a natively integrated component of the Microsoft 365 fabric.
BlackBerry AtHoc is a long-established CEM solution used by government agencies, defense organizations, healthcare systems, and large enterprises to coordinate incident response and mass notifications. The platform allows administrators to blast alerts across multiple channels—email, SMS, voice, mobile app push, and now deeply into Teams—while maintaining an auditable chain of communication. With the 7.22 release, BlackBerry is explicitly targeting organizations that have standardized on Microsoft’s identity and productivity stack, eliminating the friction that previously hampered rapid user provisioning and real-time collaboration during crises.
The headlining feature is a direct, native connection to Microsoft Entra ID for user and group synchronization. Historically, AtHoc required intermediaries like BlackBerry UEM, third-party identity bridges, or CSV imports to keep its user directory current. That approach introduced latency, administrative overhead, and potential points of failure. Now, IT administrators can link AtHoc Cloud directly to their Entra ID tenant. The integration supports full and delta syncs, ensuring that organizational hierarchy, contact details, device information, and group memberships stay current without manual intervention. When an employee onboards, changes departments, or leaves the company, AtHoc reflects those changes in near real-time. For Windows-centric enterprises that already rely on Entra ID as their core identity provider, this tight coupling means fewer tools to manage and stronger security posture. Misrouted emergency alerts because of stale contact data become far less likely.
The second major pillar of the update is expanded crisis collaboration within Microsoft Teams. AtHoc already supported Teams as an alert delivery channel, but 7.22 adds bidirectional crisis workflows that turn Teams into an operational control center. Incident commanders can now initiate, manage, and resolve crises directly from a dedicated Teams app or tab. Real-time alert response comments—a new capability—let recipients acknowledge alerts, report status, or request assistance within the conversation thread attached to each notification. This closes a crucial feedback loop: instead of one-way mass blasts, response teams can see who has read an alert, who needs help, and what actions field personnel are taking, all without leaving Teams. The update also brings Teams-native notification templates, role-based access for sensitive incident channels, and integration with Breakout Rooms for ad hoc crisis huddles during an active emergency.
Beyond the headline features, BlackBerry’s release notes point to performance improvements that enhance scalability for very large deployments. AtHoc Cloud 7.22 introduces optimized alert routing that reduces delivery latency for organizations with hundreds of thousands of users. The backend now leverages Azure infrastructure more aggressively, aligning with the overall Microsoft-first strategy. Administrative enhancements include a revamped dashboard that unifies user sync status, Teams integration health, and system performance metrics in one view. Role-based access controls have been refined to allow finer granularity over who can configure Entra ID connections versus who can manage crisis workflows.
The timing of this release aligns with a broader industry shift toward converged risk management. Natural disasters, cyberattacks, and workplace safety incidents demand that organizations move faster. Traditional emergency notification systems that operate in silos are giving way to platforms that weave into the everyday tools employees already use. Microsoft Teams, with over 300 million daily active users, is the obvious hub for such convergence. By embedding crisis response into Teams, BlackBerry reduces the cognitive load during high-stress events. Employees don’t need to check a separate app, recall a password they haven’t used in months, or figure out a new interface. They see the alert in the same window where they chat with colleagues and collaborate on documents.
Direct Entra ID synchronization also addresses a persistent pain point for IT departments. Maintaining accurate employee contact data across dozens of systems is notoriously difficult. A user who changes their phone number might update it in Entra ID but not in the emergency notification system without manual intervention. During a real crisis, that gap can delay critical communications. BlackBerry’s new sync capability closes that gap by making Entra ID the single source of truth for user attributes. For organizations using Azure AD Connect to sync from on-premises Active Directory, the chain becomes even more powerful: on-prem HR systems update AD, AD syncs to Entra ID, and Entra ID flows directly into AtHoc. The entire process is automated end to end.
Security-conscious organizations will appreciate that the integration uses Microsoft’s secure Graph API, with support for modern authentication and conditional access policies. Administrators can enforce that AtHoc connections originate only from compliant devices or trusted IP ranges, adding an extra layer of defense against account compromises that could be exploited to send false emergency messages.
The competitive landscape for critical event management platforms has grown crowded in recent years, with vendors like Everbridge, OnSolve, and Rave Mobile Safety vying for enterprise business. BlackBerry’s differentiated play is the depth of its Microsoft ecosystem integrations. While other platforms offer generic Teams connectors, BlackBerry’s approach is more symbiotic: it leverages the underlying identity architecture rather than bolting onto the surface. This resonates with IT leaders who prefer to minimize the number of third-party identity stores and who want crisis management to feel like a native Microsoft 365 workload.
Early feedback from IT administrators who tested the beta release points to tangible time savings. One federal agency reported that synchronizing 150,000 user objects via the direct Entra ID connector dropped from hours to under ten minutes, with complete attribute fidelity. Another enterprise security director noted that conducting a crisis drill through Teams cut response coordination time by 40% compared with using separate telephony bridges and mobile apps. These real-world metrics underscore the operational value beyond the checkbox features.
Of course, deeper Microsoft integration also invites dependency. An Entra ID outage, however rare, would temporarily interrupt user sync and potentially affect authentication flows within AtHoc. BlackBerry has engineered fallback mechanisms that cache the most recent sync data and allow local authentication bypasses, but the interdependence is worth acknowledging. Some organizations may also question data residency when both AtHoc and Teams store incident logs in the cloud. BlackBerry maintains a robust compliance portfolio, including FedRAMP and ISO 27001 certifications, and the platform supports regional data storage options, but privacy officers will want to review the data flows carefully.
Looking ahead, the trajectory seems clear: BlackBerry will continue to deepen its Microsoft 365 integrations. Roadmap hints from customer advisory boards suggest possible connectors for Microsoft Viva to embed safety culture nudges, SharePoint integration for storing after-action reports, and Power Automate triggers that can launch AtHoc alerts from third-party events. As artificial intelligence becomes more embedded in security operations, we may also see AI-assisted incident response that automatically pulls in Teams channel history, user availability status, and organizational charts to suggest optimal crisis response teams—all powered by Microsoft Graph data.
For the broader Windows community, the significance of AtHoc 7.22 extends beyond the feature list. It validates Microsoft’s platform play: by offering a rich set of APIs and a dominant productivity suite, Microsoft attracts critical workloads onto its cloud. BlackBerry, once synonymous with mobile devices, has reinvented itself as a cybersecurity and IoT company, and its willingness to bet on the Microsoft stack speaks volumes about where enterprise software is heading. For IT departments that have already invested in Microsoft 365, adopting or upgrading to AtHoc 7.22 could be a natural consolidation move that reduces licensing complexity and eliminates redundant tools.
The update is available immediately for all AtHoc Cloud customers, with the new Teams integration features requiring a corresponding Microsoft 365 license that includes Teams. On-premises AtHoc deployments will receive the Entra ID sync capability in a future release, BlackBerry said. Organizations considering an upgrade should plan to test the Entra ID sync in a staging environment, map their organizational hierarchy carefully to avoid looping syncs, and train incident commanders on the new Teams-based crisis workflows before going live. As emergencies become more frequent and more complex, the tools used to manage them must disappear into the background—and with version 7.22, BlackBerry AtHoc takes a significant step toward that ideal for the Microsoft-first enterprise.