Deploy where your data already lives.
Concurrence runs on Microsoft Azure in your region and writes its data into storage you own, where Microsoft Fabric and Azure Databricks read it in place. No new cloud, no second data platform.
Microsoft partner · Built on Azure · Transactable on Microsoft Marketplace
Build healthcare applications on Microsoft Azure.
Concurrence connects the data your healthcare workflows need and builds applications that work with your existing Azure environment.
Build healthcare applications on Microsoft Azure.
Concurrence connects the data your healthcare workflows need and builds applications that work with your existing Azure environment.
Transactable onMicrosoft Marketplace
Built on Azure
Built on AzureConcurrence lives in your existing Microsoft ecosystem.
Leverage your existing budget.
Concurrence is transactable on Microsoft Marketplace. Purchase through your existing Microsoft agreement, consolidate billing on your Azure invoice, and apply eligible spend to your Microsoft Azure Consumption Commitment (MACC).
Learn from your healthcare data.
Every Concurrence workflow generates interaction-level data that enriches your understanding of the patient, helping you discover which care pathways produce the best clinical and operational outcomes.
01
Your data stays yours
You own the storage and the keys.
Concurrence writes to your Azure Data Lake Storage, which stays private and encrypted with your own keys.
You decide what our agents can see.
Agents read patient context only from the tables you choose to share, whether in your Fabric lakehouse or Unity Catalog, and every user and data grant is managed through Microsoft Entra ID.
02
Works with the data platform you already run
If you’re on Microsoft Fabric:
Concurrence tables appear in your Fabric lakehouse through OneLake shortcuts, with no copies and no new pipelines. Agent activity and patient outcomes flow into Power BI through Direct Lake, so leaders see results in the reports they already use.
If you’re on Azure Databricks:
Concurrence tables land in your Azure Databricks workspace and are governed through Unity Catalog, so your teams work with them the same way they work with the rest of your data.
If you run both:
Mirrored Azure Databricks Unity Catalog lets Fabric read Concurrence tables governed in Databricks, without duplicating them, so both teams work from a single source of truth.
03
AI that stays in your region
Private, in-region model calls.
Concurrence calls Microsoft Foundry models over a private endpoint, in your own Foundry deployment or ours, so every call stays in your region.
04
Enterprise-grade by design
Runs on infrastructure your IT team knows.
The Concurrence runtime is built on Azure Kubernetes Service, Azure Database for PostgreSQL, and Azure Event Hubs, giving you the scale, reliability, and governance you expect from Azure.
Three components come together as a self-learning system, all running on Azure.
Component 1
The Health World Model
A longitudinal view of the patient, built by unifying every source of healthcare data into a single foundation: EHR records, claims, labs, device data, scheduling, prior conversations, care plans, consent and preferences.
Component 2
AI-powered workflows
Concurrence deploys AI-powered workflows across the patient and clinician journey (intake, scheduling, outreach, documentation, referrals, follow-up, etc.), each with access to the living context in the Health World Model. This lets your organization scale the judgment of expert clinicians and generate interaction-level data that has never been captured.
Component 3
Patient Trajectories
From this data, Concurrence identifies Patient Trajectories that connect specific interventions to specific outcomes. Across millions of them, your organization discovers which care pathways produce the best outcomes for each population.
The Concurrence Digital Residency
Simulate care workflows before rollout.
Create digital twins of every patient in your Health World Model and train your workflows across millions of simulated scenarios. We hydrate your environment with synthetic patient data to test realistic scenarios, edge cases, and user experience before release. Agents must prove their reliability on accuracy, empathy, and harm prevention before a single real deployment.
0 minResponse time
100%Pass rate on clinical safety metrics
98%Of patient interactions do not require human escalation
Three ways to deploy:
Microsoft Marketplace
Buy through Marketplace. Apply it to your commitment.
Concurrence is available through Microsoft Marketplace via private offer. Transactions are eligible to count toward your Microsoft Azure Consumption Commitment (MACC). No separate infrastructure contract or migration project before value.
View on Microsoft MarketplaceFind it on Microsoft Marketplace as Concurrence Data and AI Platform. Concurrence was formerly known as Amigo. Microsoft Marketplace still shows Amigo AI as the publisher of the listing.
Pricing, purchase options, and cloud commitment eligibility depend on the current marketplace listing and your agreement.
GLP-1 health coaching, tested across patient populations.
Concurrence built a GLP-1 health coach for Hims & Hers that used models on Microsoft Foundry for coaching conversations and longitudinal patient memory. Before release, Concurrence ran simulated conversations across different synthetic patient populations and scenarios to evaluate the coaching experience.
GLP-1 health coaching, tested across patient populations.
Concurrence built a GLP-1 health coach for Hims & Hers that used models on Microsoft Foundry for coaching conversations and longitudinal patient memory. Before release, Concurrence ran simulated conversations across different synthetic patient populations and scenarios to evaluate the coaching experience.
Security & compliance
Built for the standards
healthcare demands.
Independently assessed security and privacy, on Azure services covered by Microsoft's BAA.
Visit our security page
HIPAA
PHI-safe by design. Concurrence runs on Microsoft Azure services covered under Microsoft's BAA, and model calls are made through Azure-hosted endpoints with zero data retention.
SOC 2 Type II
Independently audited controls across security, availability, and confidentiality.
GDPR
EU/DE data residency deployed in production.
PHI stays in your region
Your storage is the system of record. Deployed in your own subscription, patient data never leaves your tenant. In the Concurrence-managed options, our runtime processes PHI in your region under our BAA and SOC 2 controls.
Your controls, built in
Identity through Microsoft Entra ID, customer-managed keys in your Azure Key Vault, and Concurrence audit logs delivered to your Azure Monitor. Deployed in your own subscription, your existing governance applies on day one.
Meet your EHR where it is.
We enable bidirectional, read and write integrations with leading EHR and care delivery platforms using industry standard HL7v2 and FHIR interfaces. Based on your team’s use cases, we will scope out the correct integration mechanisms and endpoints. Our team brings knowledge from building 100+ health system vendor integrations.
Concurrence on Microsoft Azure: key questions
What is Concurrence on Microsoft Azure?
Concurrence is a healthcare data and AI platform that runs on Microsoft Azure. It unifies patient data into a Health World Model, deploys AI-powered workflows across the patient and clinician journey, and identifies Patient Trajectories that connect specific interventions to specific outcomes.
Is Concurrence available on Microsoft Marketplace?
Yes. Concurrence Data and AI Platform is listed on Microsoft Marketplace and is available through a private offer. Concurrence was formerly known as Amigo, and the listing currently shows Amigo AI as its publisher.
Can a Marketplace purchase count toward a Microsoft Azure Consumption Commitment (MACC)?
The listing carries the Azure benefit eligible badge, so eligible purchases made through Marketplace in the Azure portal count toward your Microsoft Azure Consumption Commitment. Pricing, purchase options, and commitment eligibility depend on the current listing and your agreement with Microsoft.
How can Concurrence be deployed on Azure?
There are three options: a dedicated Azure subscription in your region managed by Concurrence, an Azure managed application in your own subscription, or a shared Concurrence environment in your region with each customer isolated in layers.
Does Concurrence work with Microsoft Fabric and Azure Databricks?
Yes. With Microsoft Fabric, Concurrence tables appear in your lakehouse through OneLake shortcuts without copies, and outcomes flow into Power BI through Direct Lake. With Azure Databricks, Concurrence tables land in your workspace and are governed through Unity Catalog. If you run both, mirrored Azure Databricks Unity Catalog lets Fabric read the same tables.
Where is patient data stored and processed on Azure?
Your storage is the system of record. When Concurrence is deployed in your own subscription, patient data never leaves your tenant. In the Concurrence-managed options, the Concurrence runtime processes PHI in your region under a BAA and SOC 2 controls. Model calls use Microsoft Foundry over a private endpoint, so every call stays in your region.
Learn more about the Concurrence platform, our partnership with Databricks, security and compliance, and global availability.