Cosmos DB

And so to answer your question, that lower tier is like easily accessible information that candidates ask every single day, every single hour.

When we start to crawl up to Cosmos and Azure, which our stack sits on Azure Cosmos and Recruiter Flow as our ATS, there's a little plug Recruiter Flow.

Azure at the very top collects all of our historical data, right? Which is pivotal to anybody who's claiming to be AI native is the fact that we're able to create containers for each one of our clients to actually get smarter over time, right? Which is something, again, to your first question, Ben, an ATS can never do, right? When it sits inside of Azure or a cloud platform, that is our true source of truth, which allows us to create these, what are called containers, so that we can over time start to know what types of candidates this client looks for, what types of screening questions this client looks for, and what type of copywriting do these candidates convert at a higher clip for.

That is an intelligence layer that needs to sit way above your ATS, which at very ground level is just there to communicate with candidates 24-7.

It doesn't decide what the message means operationally, it decides where the message should go.

IoT Hub can route device-to-cloud messages to Azure Event Hubs, Azure Storage, Azure Service Bus queues or topics, and on paid IoT Hub tiers that support it, Azure Cosmos DB.

Each destination fits a different downstream job, so naming the endpoint alone doesn't finish the design.

Event Hubs usually fits when you need a stream that several independent consumers can read.

Azure Storage fits when you need an economical raw record that can support later inspection, audit work, or batch processing.

Service Bus can fit when telemetry produces a defined business message that an application must process through a queue or topic pattern.

Cosmos DB can fit selected operational application patterns where low-latency document access makes sense.

None of those choices turns telemetry into a business decision.

And as I said earlier, Where does the responsibility of Microsoft end? Well, once you start deploying and you choose to deploy only in one region, well, yeah, tough break.

Microsoft will not be held responsible for your application to move unless you say, of course, I want an auto failover, let's say with my Cosmos DB to another region because I designed it that way or where I have a read-only copy there for that matter.

These are things that you can have in your own control because you designed them that way.

But out of the box, a lot of these services are not being enabled by a checkbox out of the box.

Think about new services like, not all new services, think about Azure Site Recovery.

Think about...

Cosmos DB, all these services have these capabilities to quickly fail over into another region or into another zone for that matter, and making sure that your service stays up and running.

But 100%, forget about that.

I need to dig into this feature a bit more because I'm not exactly sure what this means.

It says managing SQL Server, Azure SQL, PostgreSQL, Cosmos DB, and SQL Database and Fabric.

It sounds to me like this is going to bring data from other sources, Azure-based services, and put them in one single place.

And I really...

instead of like so fabric has cosmos db in it fabric has sql databases in it fabric does not have postgres right so i kind of i kind of would like them to say i kind of want to like yes i understand this is management but why would i go to fabric to manage all my databases it doesn't I guess I'm just not quite clear on why I would want me to go into Fabric to manage the databases.

It makes more sense to me to like, I'm going to Fabric to manage the databases that I put in Fabric.

There could be a lot of those.

Walk me through the history and the meeting, ideally, where someone says, yeah, this name, no confusion here at all.

Well, so Cosmos DB was originally named DocumentDB.

And then so Microsoft holds the DocumentDB trademarks and copyrights.

However, AWS for Amazon DocumentDB, I think the combination of both of them, they have the copyright.

And so now we have DocumentDB, the open source project, we have Amazon DocumentDB, And nowadays, even Azure DocumentDB.

So there's DocumentDB all over the place.

And I had in the beginning, people come to me and said, hey, this DocumentDB isn't that like an open source Cosmos DB? And I say, no, it's completely different database.

Yeah, it's not the same.

Microsoft patches CVSS 10.0 Azure AI Foundry flaw Microsoft patch CVE-2026-85889, CVSS 10.0, a missing authentication flaw in Azure AI Foundry allowing unauthorized privilege escalation over a network.

no customer action required server-side fix deployed also patched cvss 9.9 command injection in microsoft 365 copilot cvss 9.9 improper authorization in azure database for postgre sql cvss 9.6 neutralization flaw in azure cosmos db no evidence of exploitation and three additional cves see show notes for the full list sources the hacker news security week Windows 11 26H1 out-of-band updates Microsoft shipped out-of-band updates for Windows 11 version 26H1 addressing CVE-2026-62721.

CVSS 7.8 in Windows user mode power service enabling local privilege escalation to system and CVE2026-85921.

CVSS 8.2, double free in Windows secure kernel mode, enabling escalation to VTL1 privileges.

It doesn't decide what the message means operationally, it decides where the message should go.

IoT Hub can route device-to-cloud messages to Azure Event Hubs, Azure Storage, Azure Service Bus Queues or Topics, and, on paid IoT Hub tiers that support it, Azure Cosmos DB.

Each destination fits a different downstream job, so naming the endpoint alone doesn't finish the design.

Event Hubs usually fits when you need a stream that several independent consumers can read.

Azure Storage fits when you need an economical raw record that can support later inspection, audit work, or batch processing.

Service Bus can fit when telemetry produces a defined business message that an application must process through a queue or topic pattern.

Cosmos DB can fit selected operational application patterns where low latency document access makes sense.

None of those choices turns telemetry into a business decision.