[MS] Now Generally Available: Cosmos DB Mirroring in Microsoft Fabric with Private Networks - devamazonaws.blogspot.com

We’re excited to announce the general availability of private network support for Azure Cosmos DB mirroring in Microsoft Fabric, enabling customers to replicate operational data into Fabric from Azure Cosmos DB accounts secured with private endpoints or virtual networks while continuing to operate within their existing network security models. As more organizations connect operational data with analytics and AI to power new insights and intelligent applications, the ability to do so securely has become increasingly important—making private network support a key capability for bringing operational data into Fabric without compromising established security boundaries.

Bringing secured operational data into Fabric

Azure Cosmos DB mirroring makes it easy to continuously replicate operational data into Microsoft Fabric, where it can be used across analytics and AI experiences without building and maintaining custom ingestion pipelines. With private network support now generally available, customers can use mirroring with Cosmos DB accounts that operate within restricted network environments, bringing secured operational data into Fabric while preserving their existing security posture.

Get Started by Configuring Mirroring with Private Networks

Configuring mirroring for Cosmos DB accounts that use private endpoints or virtual networks involves a small number of setup steps. Selected Networks enabled for Cosmos DB Account To see these steps in detail, refer to How to: Configure private networks for Azure Cosmos DB Fabric Mirroring. The documentation includes a PowerShell script that can automate the required networking and authorization configuration, allowing you to focus on creating the mirrored database in Fabric. Here are the steps at a high level.
  1. Assign the required RBAC policies for Mirroring.
  2. Temporarily secure your Cosmos account with required Azure Service Endpoint IPs (or use Network Security Perimeter).
  3. Configure a Network ACL from your Fabric Workspace to your Cosmos account.
  4. Create the new Mirrored database in Fabric.
  5. Restore the original network configuration once setup is complete.
For Cosmos DB accounts using Private Endpoints, step 2 involves temporarily enabling Selected networks to allow required Azure service access during the initial mirroring configuration. This access is scoped to specific Azure service endpoints and is only required during setup. After the mirroring connection is established, customers can restore their original network settings and continue operating with restricted network access. For detailed guidance and step‑by‑step instructions, see How to: Configure private networks for Azure Cosmos DB Fabric Mirroring. About Azure Cosmos DB Azure Cosmos DB is a fully managed and serverless NoSQL and vector database for modern app development, including AI applications. With its SLA-backed speed and availability as well as instant dynamic scalability, it is ideal for real-time NoSQL and MongoDB applications that require high performance and distributed computing over massive volumes of NoSQL and vector data. To stay in the loop on Azure Cosmos DB updates, follow us on X, YouTube, and LinkedIn.  Join the discussion with other developers on the #nosql channel on the Microsoft Open Source Discord.
Post Updated on March 16, 2026 at 01:00PM
Thanks for reading
from devamazonaws.blogspot.com

Comments

Post a Comment

Popular posts from this blog

[MS] Pulling a single item from a C++ parameter pack by its index, remarks - devamazonaws.blogspot.com

In my earlier discussion of pulling a single item from a C++ parameter pack by its index , I noted that with the Pack Indexing proposal, you would be able to write this to pull an item from a parameter pack while preserving its reference category. template<int index, typename...Args> void example(Args&&... args) { auto&& arg = (Args...[index]&&)args...[index]; using Arg = Args...[index]&&; } Why did I need to apply the (Args...[index]&&) cast ? Why can't I just write this: auto&& arg = args...[index]; or possibly decltype(auto) arg = args...[index]; Well, when you write the name of a variable, the result is an lvalue reference, even if the variable is an rvalue reference . Watch: struct S { S(S&); // construct from lvalue S(S&&); // construct from rvalue }; void whathappens(S&& s) { S t = s; // which will it use? } Try it out in your favorite compiler. This code construc...
Read more

[MS] Debugger breakpoints are usually implemented by patching the in-memory copy of the code - devamazonaws.blogspot.com

In practice, when you set a code breakpoint in the debugger, the debugger replaces the instruction at that location with a breakpoint instruction.¹ When execution reaches that instruction, it will encounter the breakpoint instruction and break into the debugger. When the program has been stopped in the debugger, what happens next can vary from debugger to debugger. Some debuggers remove all their breakpoints when the program stops, and then restore the breakpoints when the program resumes. Other debuggers leave the breakpoints in place even when the program is stopped. In both cases, if you inspect the memory in the debugger, you will see the original unpatched code. In the first case, it's because the code really is unpatched; the breakpoint instructions are removed. In the second case, it's because the debugger is lying to you and showing you the original bytes even though they aren't what are in memory right now. Most of the time, this deception is insignificant. Eve...
Read more

[MS] The case of the crash when destructing a std::map - devamazonaws.blogspot.com

A customer reported that they were getting crashes while destructing a std::map . Here's the point of the crash: eax=245bd25c ebx=00004d33 ecx=31feece4 edx=00c40000 esi=00000000 edi=31feece4 eip=563397db esp=245bd250 ebp=245bd268 iopl=0 nv up ei ng nz na pe nc cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010286 contoso!std::_Tree<⟦...⟧>::~_Tree+0x2b: 563397db cmp byte ptr [esi+0Dh],0 ds:002b:0000000d=?? 0:054> k9 ChildEBP RetAddr (Inline) -------- contoso!std::_Tree_val<⟦...⟧>::_Erase_tree [xtree @ 1073] (Inline) -------- contoso!std::_Tree_val<⟦...⟧>::_Erase_head+0x5 [xtree @ 1073] 245bd268 56338313 contoso!std::_Tree<⟦...⟧>::~_Tree+0x2b [xtree @ 1073] 245bd290 56362695 contoso!Contoso::IdCollection::~IdCollection+0x163 245bd2b4 564c8510 contoso!Contoso::LogEntry::~LogEntry+0xd5 245bd2e0 5691a999 contoso!Contoso::LogEntries::Cleanup+0x90 (Inline) -------- con...
Read more