https://thedotnetblog.com/tags/operations/Articles, tutorials and insights from the .NET community.Hugoen@thedotnetblog (The .NET Blog)@thedotnetblogThu, 25 Jun 2026 00:00:00 +0000https://thedotnetblog.com/news/emiliano-montesdeoca/azure-storage-migration-tooling-confidence-and-fit/Thu, 25 Jun 2026 00:00:00 +0000Emiliano Montesdeocahttps://thedotnetblog.com/news/emiliano-montesdeoca/azure-storage-migration-tooling-confidence-and-fit/The latest Azure Storage migration guidance is less about one magic migration tool and more about choosing the right combination of planning, online movement, and offline transfer. That is the practical story worth noticing.<p>Storage migration content can easily become too abstract or too sales-heavy.</p> <p>What I found more useful in this Azure update is the practical framing: storage migration is not one problem. It is a sequence of decisions around planning, movement, synchronization, risk, and confidence.</p> <p>That is a much more honest way to talk about it.</p> <h2 id="the-useful-part-is-the-combination-not-a-single-tool">The useful part is the combination, not a single tool</h2> <p>The post brings together:</p> <ul> <li>Azure Migrate</li> <li>Azure Copilot Migration Agent</li> <li>Azure Storage Mover</li> <li>Azure Data Box</li> </ul> <p>And the real point is that different migration shapes need different answers.</p> <p>Some workloads need assessment and dependency sequencing.</p> <p>Some need online sync.</p> <p>Some need offline transfer because the network is not the right answer.</p> <p>That is what makes this guidance more practical than the usual “just use product X” pitch.</p> <h2 id="my-take">My take</h2> <p>This is not the most developer-centric story in the batch, but it still has value because modernization often stalls on data movement long before application changes are done.</p> <p>If teams want to modernize systems on Azure, getting the migration planning and tooling choice right is part of the job.</p> <p>That is the real takeaway here.</p> <p>Original post: <a href="https://azure.microsoft.com/en-us/blog/modernize-your-data-with-azure-storage-plan-and-migrate-with-confidence/">Modernize your data with Azure Storage: Plan and migrate with confidence</a></p>https://thedotnetblog.com/news/emiliano-montesdeoca/agentic-cloud-operations-from-observability-to-action/Wed, 24 Jun 2026 00:00:00 +0000Emiliano Montesdeocahttps://thedotnetblog.com/news/emiliano-montesdeoca/agentic-cloud-operations-from-observability-to-action/The latest Azure vision for agentic cloud operations is notable because it connects observability, governance, and optimization into a single loop. The real story is moving from cloud insight to controlled action.<p>Cloud operations has had no shortage of dashboards for years.</p> <p>What teams usually do <em>not</em> have is a clean path from signal to action.</p> <p>That is why the latest Azure write-up on <strong>agentic cloud operations</strong> is interesting. The strongest idea in it is not just that AI can summarize telemetry. It is that observability, governance, and optimization are being framed as parts of the same loop.</p> <p>That is the part I think matters.</p> <h2 id="observability-is-only-useful-if-it-shortens-the-path-to-action">Observability is only useful if it shortens the path to action</h2> <p>Most teams already have alerts, metrics, traces, and logs. The problem is usually not a lack of data.</p> <p>The problem is:</p> <ul> <li>too much signal</li> <li>too much correlation work done manually</li> <li>too much delay between detection and response</li> </ul> <p>The Azure story here is trying to connect those steps more tightly. Observability becomes context for AI-assisted reasoning, and that reasoning can feed optimization and remediation workflows under policy.</p> <p>That is a stronger operating model than “AI explains the dashboard.”</p> <h2 id="governance-is-the-non-optional-part">Governance is the non-optional part</h2> <p>I also like that the post does not treat governance as an afterthought.</p> <p>If agents are going to influence cloud operations, governance has to be part of the execution path:</p> <ul> <li>access control</li> <li>policy boundaries</li> <li>auditable actions</li> <li>human approval where needed</li> </ul> <p>Without that, you do not have agentic operations. You have automated chaos with better marketing.</p> <h2 id="my-take">My take</h2> <p>The phrase “agentic cloud operations” only becomes meaningful if the platform can reliably connect:</p> <ol> <li>detection</li> <li>reasoning</li> <li>action</li> <li>feedback</li> </ol> <p>This Azure direction is interesting because it is trying to build exactly that loop.</p> <p>We are still early, but the framing is right.</p> <p>Original post: <a href="https://azure.microsoft.com/en-us/blog/from-insight-to-action-the-next-phase-of-agentic-cloud-operations/">From insight to action: The next phase of agentic cloud operations</a></p>