Your organization can connect to its own AI service to enable advanced AI capabilities within the Qmarkets platform.
This approach - often called Bring Your Own Key (BYOK) - lets your data stay under your full control while enabling Qmarkets to generate AI-driven insights and content using your internal AI models.


Note:
Currently, Azure OpenAI is the only supported BYOK provider.
If you would like to connect to another BYOK provider, please inform your CSM.

The estimated time to evaluate and support new providers is 2-4 weeks.


Process Overview

The setup is lead by Qmarkets team, and based on the following steps:

  1. Customer side:
    • Providing the API Endpoint
    • Confirming the default parameters for Max Tokens, Temperature, and Presence OR providing new parameters,
    • Whitelist the Qmarkets server’s IP address or domain in your Azure OpenAI configuration
    • Informing Qmarkets
  2. Qmarkets side:
    • Completing setup based on the provided information
    • Basic sanity testing
  3. Qmarkets will inform the customer's POC when the AI capabilities are available.


1. API Endpoint and other relevant parameters.


To proceed, your IT team will need to provide:

  • API Endpoint – your deployed Azure OpenAI endpoint (e.g., https://your-resource-name.openai.azure.com/)

  • API Key – your organization’s Azure OpenAI API key


These are the parameters which are being used by default:

  • Azure API Version – typically set to latest

  • Qmarkets uses the following defaults unless instructed otherwise:

    • Max tokens: 5,000 → allows reasonably rich output without waste

    • Temperature: 1 → keeps responses creative enough for ideation workflows while still grounded

    • Presence: 0 → avoids forcing topic changes, prioritizing relevance

      These settings cover most innovation-management scenarios (idea summarization, campaign text refinement, etc.)
      If you have stricter generation requirements - e.g., more deterministic behavior - let us know and we’ll tune accordingly.


2. Network / Whitelisting

To establish secure access, your Azure firewall must allow incoming requests from Qmarkets’ static server IP address(es) or domain.
These values rarely change; we’ll send them as part of onboarding so your firewall team doesn’t have to chase updates.

All traffic uses HTTPS.

Additional Information

What Data Is Sent to Azure

Requests can include contextual text you provide within Qmarkets, for example:

  • Company name / description

  • Idea title / description

  • Campaign description

  • Optional workflow fields

PII is intentionally excluded.


Note: If a field contains PII because someone typed it into an idea description, that text will be forwarded as-entered - so your internal governance rules still apply.

Data Governance & Compliance

  • Azure OpenAI does not use your data to train models unless explicitly configured by your organization.

  • Data remains processed within your Azure tenant boundaries.

  • Qmarkets processes AI prompts only as needed for generation; we do not reuse them for training or analytics.

  • Our implementation is designed to align with enterprise privacy standards such as GDPR.

You control the model, the data flow, and the retention policy.

Error Handling & Monitoring

  1. AI Data self-admin area
    Logs prompts, responses and tokens to help you:

    • Review usage

    • Analyze quality

    • Demonstrate compliance

    • Support audit needs

  2. Internal watchdog logging
    All API failures (timeouts, bad keys, quota issues) are recorded on our side.
    Qmarkets engineers can review these logs if troubleshooting is needed.