Product support
Include identifiers and timestamps, not secrets
Account ID, device ID, session ID, client version, time and error code help support reproduce issues safely.
CONTACT
Give the right team
the facts they need.
Product support, business enquiries and security reports use separate handling paths. Never send passwords, verification codes, device private keys or remote-session content.
Trusted native remote sessionsWeb manages identity and authorization; native clients carry control and media.
Business enquiries
Describe scale and governance needs
Device count, member count, regions, audit, identity and deployment requirements help match the right plan.
Security reports
Preserve evidence and use the security path
Account takeover, authorization bypass and vulnerability reports should retain relevant audit identifiers without sharing remote content.
Start with secure remote access, then add what you need.
Core remote access remains simple; advanced performance and governance are enabled by published entitlements.