BlackBerry has quietly shipped AtHoc Cloud 7.22, and for Windows administrators overseeing emergency-communication platforms, a single change will look familiar yet overdue: the update replaces a manual sync client with automated Microsoft Entra ID synchronization, aiming to ensure that alert rosters always match the directory.

The release arrived June 30, bringing direct integration with Microsoft’s cloud identity service for the first time while leaving existing Teams-based collaboration tools in place. The result is a tightening of the relationship between the critical-event management system and the Microsoft stack many enterprises already use.

What actually changed inside AtHoc 7.22

AtHoc, BlackBerry’s platform for sending mass notifications, tracking personnel accountability, and gathering field intelligence during crises, has long offered a Windows-based User Sync Client. That tool required administrators to export user data from a directory, format it, and import it into AtHoc on a schedule. With version 7.22, the sync client is deprecated in favor of a cloud-to-cloud connection that pulls user records directly from Entra ID.

The integration focuses on two data flows: user lifecycle attributes (name, department, location, contact points) and group memberships. When a new employee appears in Entra ID—or when someone changes roles or leaves—AtHoc reflects the change automatically. For organizations that rely on role- or location-based alerting, the shift eliminates the manual step that often caused stale data to linger between sync cycles.

A secondary feature in the update adds “alert-response comments,” allowing recipients to attach brief contextual notes to their acknowledgment. Instead of a binary “safe” or “not safe,” an operator might see “basement flooded, heading to rally point B.” It is a small addition, but one that can sharpen situational awareness during a live event.

BlackBerry’s own documentation and the official 7.22 release notes confirm these changes. The company has also clarified that the existing AtHoc Publisher and Messaging apps for Microsoft Teams remain unchanged—they continue to surface alerts inside the collaboration tool—but the 7.22 work concentrates on the identity pipeline behind those notifications.

What an automated identity sync means for you

For IT administrators and security operations teams, the practical impact breaks into three buckets.

Directory hygiene becomes an incident-response concern

A crisis alert is only as good as its recipient list. If a retired account still sits in the alert group, the operator wastes time chasing false positives. If a new hire is missing, critical personnel stay uninformed. By tying AtHoc’s contact data directly to Entra ID, the platform offloads trust to the same directory that already governs email, Teams, and device access. That alignment means changes made in Entra ID—whether via HR system sync, PowerShell, or the admin center—propagate to AtHoc without extra steps.

The implication for Windows shops is clear: clean up Entra ID and you clean up AtHoc. Conversely, sloppy attribute management now has a new risk surface.

Testing becomes non-negotiable

Automation does not mean hands-off. Admins should treat the sync as a new integration that requires the same validation as any identity federation. Specifically:

  • Confirm which Entra ID attributes and security groups will drive AtHoc targeting. (BlackBerry’s admin guide recommends limiting the scope to essential fields to avoid clutter.)
  • Simulate joiner, mover, and leaver scenarios in a staging environment before promoting to production.
  • Verify that Teams app permissions, alert templates, escalation rules, and data retention policies align with compliance requirements after the sync is live.

In an organization that handles classified or sensitive incident communications, an automated sync introduces new data flows between Microsoft’s cloud and AtHoc’s infrastructure. Security teams should review the connection’s authentication method (OAuth-based app registration) and the data residency implications.

End users will notice smoother targeting, not the plumbing

For the frontline employee who simply needs to get an emergency alert on their phone, laptop, or desk phone, the Entra ID sync is invisible. The benefit shows up indirectly: they stop receiving messages meant for someone in a different building. Or they do receive the alert because their department code was finally correct. The addition of comment feedback might also appear in the AtHoc mobile app or Teams interface, giving them a chance to provide quick context.

For organizations still evaluating AtHoc, the lower sync maintenance burden removes a deployment hurdle. The configuration checklist for a new installation shrinks by one manual component.

How we got here: the gradual Microsoft alignment

BlackBerry’s pivot from consumer handsets to enterprise security software has been underway for nearly a decade, but the AtHoc product’s Microsoft journey is more recent. Acquired in 2015, AtHoc initially integrated with on-premises directories via the sync client. The product added a Teams messaging integration in 2023, allowing operators to publish alerts to Teams channels and start two-way conversations. A Teams Publisher app followed, enabling administrators to manage alert templates from within Teams.

Version 7.22, however, represents the first direct, native cloud-to-cloud tie with Entra ID. The move mirrors a broader pattern among enterprise SaaS platforms: as Microsoft’s identity service becomes the default directory for Windows and Microsoft 365 environments, third-party tools that plug into it eliminate friction and reduce support tickets. For BlackBerry, the timing also coincides with a period of renewed focus on Secure Communications revenue. In its fiscal Q1 2027 filing (quarter ended May 31, 2026), the company reported $73.6 million from that division, though growth was led primarily by the SecuSUITE product rather than AtHoc.

The financial narrative underscores that AtHoc’s integration story is not a sudden pivot but a steady evolution. The company raised its fiscal 2027 revenue guidance to $594–$621 million in the same report, hinting that partners like Microsoft are part of the sales conversation, if not yet a dramatic revenue driver.

What to do now: your AtHoc 7.22 upgrade checklist

If your organization runs AtHoc Cloud and uses Entra ID, the upgrade path is straightforward, but the planning steps deserve attention.

  1. Verify your AtHoc version. The sync change is available in AtHoc Cloud 7.22. If you are on an earlier release, schedule an upgrade window. On-premises AtHoc deployments will not see the direct Entra ID sync without additional configuration; check with BlackBerry support.
  2. Inventory your current sync client setup. Document the existing import schedules, attribute mappings, and any custom scripts. You will recreate these mappings in the cloud admin portal.
  3. Register an Entra ID application. AtHoc’s documentation walks through creating an app registration with delegated permissions to read user profiles and group memberships. Grant consent only for the minimum required scope.
  4. Scope the synchronization. Decide whether to sync all users or a subset via security groups. Agencies handling classified data may want to exclude sensitive accounts or use separate Entra ID tenants.
  5. Map attributes carefully. Map the fields AtHoc uses for targeting—typically jobTitle, department, officeLocation, and contactMethods. BlackBerry’s defaults are sensible, but custom fields (like clearanceLevel) can be mapped if needed.
  6. Run a test. Before switching to production, sync a pilot group and send a test alert. Verify that the targeted recipients receive the notification and that their records update when you change an attribute in Entra ID.
  7. Train operators on alert-response comments. If you enable the new commenting feature, brief your incident-response team on how to interpret and act on contextual messages during a crisis.
  8. Decommission the old sync client. Once you confirm the cloud sync is stable, uninstall the Windows-based User Sync Client from the server where it ran and remove any old import jobs.

Administrators in high-compliance environments should also loop in legal and privacy teams. An automated sync means employee data flows from Microsoft’s datacenters to BlackBerry’s infrastructure continuously, which may require a data protection impact assessment.

Outlook: identity as the backbone of crisis response

BlackBerry’s Entra ID play is not revolutionary—Okta, Ping, and others have offered automated directory sync for years—but for Windows-centric enterprises already standardized on Microsoft identity, it removes a meaningful chore. The next logical step would be tighter integration with Microsoft Sentinel or Defender for real-time alert triggers based on security incidents, something BlackBerry has hinted at in its Secure Communications roadmap without committing to a date.

For now, the 7.22 release rewards shops that keep their directories tidy and punishes those that treat identity cleanup as an afterthought. In a genuine emergency, that difference could matter.