Customer Support · Microsoft Marketplace
Support for the Oracle ⇄ ADLS Bridge.
Direct engineering support from the team that built and deploys the offer. Submit the form below or email [email protected] — both route to the same intake queue and follow the response-time commitments below.
Response-time commitments
Severity-tiered support.
Initial response is measured from receipt during support hours. Outside support hours, the clock starts at the beginning of the next business day.
- Sev 1
Production down
Initial response: 1 business hour
Production extraction or restore is failing, the deployed Container Apps Job is non-recoverable, or Synapse/Fabric queries against the archive return errors that block business-critical use.
- Sev 2
Major impact
Initial response: 4 business hours
A significant feature is degraded but a workaround exists. Examples: a non-critical table fails classification, partial-job resume is not working as documented, or a Bicep deploy completes with warnings.
- Sev 3
General questions
Initial response: 1 business day
How-to questions, documentation clarifications, configuration guidance, schema-restore options, Synapse / Microsoft Fabric query patterns, and feature requests.
Support hours: Monday–Friday, 8:00am–6:00pm US Central Time (UTC−6 / UTC−5 during daylight saving), excluding US federal holidays. Tickets received outside support hours are acknowledged at the start of the next business day.
Before you submit
What to include in your request.
Including the context below in your initial message lets us reproduce the issue without a follow-up round-trip — typically cutting time-to-resolution in half.
- Azure tenant ID and subscription ID associated with the deployment
- JOB_ID of the affected extraction or restore run (printed in job logs)
- Container Apps Job name and the Azure region it is deployed to
- Oracle source version (e.g., 19c, 21c) and the failing table name(s) if applicable
- Full error message and the trailing 50 lines of stderr from the job log
- Time window (UTC) in which the issue occurred
Do not include passwords, connection strings, or Oracle wallet contents. If a credential is implicated, share only the credential name or Key Vault reference — we will coordinate a secure channel for any sensitive material we actually need.
Open a support request
Submit your ticket.
Submitting this form delivers your ticket directly to [email protected]. We confirm receipt within the response-time commitment for the severity you select.
Prefer email?
Write directly to [email protected] with the same context listed above — same intake queue, same response-time commitments.