There are two mailboxes and one booking link. Pick the one that matches what you need and a founder will take it from there.
Sales, pilots, and general questions
Write to hello@orbitrasecurity.com for anything commercial or general: a quote, a pilot, licensing, press, partnerships, or a product question the FAQ does not answer. It helps to include your Microsoft license level (Business Premium, E3, or E5), a rough user count, and what prompted you, whether an audit finding, an insurer questionnaire, or a Global Administrator count you do not like. Orbitra publishes no prices; Plans explains how a subscription is scoped and quoted.
Start with a response walkthrough
Book 30 minutes with a founder to follow one identity scenario through investigation, action review, named approval, execution, and supported verification. We can use a demonstration tenant, so no connection to your environment is needed.
If the workflow fits your team, we can arrange a read-only privilege exposure assessment of your tenant and agree the scope together. That read-only connection cannot execute a response. Review supported response actions and how Orbitra fits alongside Microsoft before the call.
Product issues
Use Report an issue in Orbitra or email hello@orbitrasecurity.com if you cannot sign in. Include the affected step and approximate time with time zone. Do not send passwords, access tokens, webhook URLs or unredacted customer content. Automatic application reports are collected separately and do not contain your support description. See how automatic reports work.
Microsoft Teams connection support
For a Teams setup or notification question, use Report an issue in Orbitra or email hello@orbitrasecurity.com, including if you do not have an Orbitra account. Include the intended workspace and region, the step involved and the approximate time with time zone. If available, include the saved test reference. Do not send passwords, access tokens, setup codes, webhook URLs or unredacted chat or incident content.
Setup and help
When the connection is enabled for your organization, an existing Orbitra workspace and an authorized workspace administrator are required. Your organization must also permit the Teams app. In the intended workspace, open Settings, then Notifications, then Connect Microsoft Teams. Add the app to the intended team, send the prepared message in the bot's personal chat, and return to the same Orbitra browser to check setup and confirm the team.
If Orbitra requests a team command, send the exact displayed command with a mention of this bot in the intended standard channel. Start a new connection in Orbitra if the code has expired. Then select a channel and event settings in Orbitra. Channel selection posts a setup message; Test sends a separate message. Private and shared channel destinations are unavailable.
When public guidance is enabled, Help, Hi or Hello in the bot's personal chat shows fixed instructions without requiring an Orbitra login. In a channel, mention the bot before the command. Adding the app, receiving a welcome or requesting help does not confirm an Orbitra connection. Response decisions and approvals take place in Orbitra.
Uncertain results and disconnecting
A provider message reference means the provider recorded a message. It does not confirm that someone received or read it. Check the selected channel and current connection status before repeating a test with an unknown outcome.
To stop Orbitra from using a connection, choose the intended workspace, open Settings, then Notifications and disconnect Teams. Remove the app separately in Teams if needed. Disconnecting does not recall messages already held by Microsoft or delete every historical record.
Read Teams data use and guidance retention for processing and cleanup details. For a data request, including an interaction without an Orbitra account, follow the privacy request guidance.
Security vulnerability reports
Send vulnerability reports to security@orbitrasecurity.com, not to the general mailbox. The security and disclosure page sets out what is in scope, the safe harbor terms, and the acknowledgement and triage targets you can hold us to.
What happens after you write
A founder replies from an @orbitrasecurity.com address within one business day, Monday to Friday. There is no sales development team in between. If you asked for a review, the reply proposes a slot; if you sent a vulnerability report, the disclosure page timelines apply. Add hello@orbitrasecurity.com to your safe senders so the reply does not land in quarantine.
Orbitra connects Microsoft identity exposure analysis to approved response and evidence. It inventories human and workload access, prioritizes supported Entra privilege paths, and re-reads Microsoft state for supported actions. A named person approves every Orbitra-executed response today. See the workflow and coverage limits, or request a read-only exposure review.
About the company
Orbitra Security is a Canadian company. Regional response and connection records use your workspace's United States or India home region. Shared ownership and authorization metadata and automatic application reports use US services. See Data use, About, Trust, or the team.