Postman v10 Desktop Agent native messaging host deployment under managed browser policies

Postman v10 replaced the Interceptor browser extension with the Desktop Agent, which relies on a native messaging host to route traffic from supported browsers. In enterprise environments where browsers are managed through Group Policy, Intune, or similar tools, the native messaging host executable (PostmanNativeMessagingHost.exe) is frequently blocked by application control policies such as AppLocker or Windows Defender Application Control because it lacks a recognized publisher signature. Postman does not provide an MSI installer or Intune Win32 app package for the native messaging host, and the documented migration path assumes user-level installation privileges. Extension ID restrictions in managed Chrome and Edge profiles further prevent the companion extension from communicating with the host even when the executable is allowed. Firefox support remains experimental and requires manual manifest placement, which is infeasible under locked-down profiles.

What deployment mechanism does Postman recommend for the native messaging host in environments that prohibit user-level executable installation and require centralized software distribution?

How should organizations configure browser policies to permit the Desktop Agent extension and native messaging host without weakening application control baselines?

Is there a timeline for an officially signed, enterprise-distributable package for the native messaging host?