News For Dev-ops

In April 2021, we announced the Microsoft Build of OpenJDK . We were starting with a preview of our Java 11 builds for Windows, Linux, and macOS. Today, if you're planning a Java upgrade on Azure, you have several generations of that work to build on: 11, 17, 21, and now 25. Java 8 has been part of that work too, with help from the fine folks at the Eclipse Foundation's  Eclipse Adoptium project . Microsoft has supported Java 8 on Azure using their Eclipse Temurin builds of OpenJDK 8, rather than producing a Microsoft Build of OpenJDK 8. That collaboration goes back to the launch: our first Java 11 builds also used Adoptium's build scripts and quality assurance suite. Supporting those releases has meant years of updates. Now it's time to plan the next move. The  Microsoft Build of OpenJDK support roadmap  lists September 2027 as the  earliest end-of-support date for Java 11 and 17 . That's a distribution-wide milestone: if you use those Microsoft builds on a VM, i...

When you're moving between an implementation, its tests, and a related interface, the order of your open tabs can become a useful part of the task. But arranging that order and returning to a particular position shouldn't require a mouse trip each time. Visual Studio 2026 version 18.11 adds keyboard commands for both jobs: move the active tab into position, then jump directly to a tab by its visual position. The connection is the tab order itself. You can arrange a small working set and navigate that arrangement from the keyboard. Put the active tab where you want it Use Ctrl + Shift + PgUp to move the active tab one position left, or Ctrl + Shift + PgDn to move it one position right. For example, move a test file next to its implementation before you start comparing them. The command moves the tab; it doesn't switch to the neighboring document. If you use vertical tabs, the same shortcuts move the active tab up or down. They also work for tool windows hosted in t...

AI agents can reason over data, invoke APIs, and coordinate complex workflows. Yet many business processes still depend on websites, including internal portals, administrative consoles, vendor systems, dashboards, and applications without complete API coverage. Browser automation tool in Microsoft Foundry is now generally available. Browser automation tool gives agents a managed browser so they can navigate websites, inspect content, complete forms, and perform multistep browser workflows using natural-language instructions. Powered by Playwright Workspaces , Browser Automation Tool brings scalable browser infrastructure, enterprise connectivity, observability, and human oversight directly into Microsoft Foundry. Browser automation for every Foundry agent Browser Automation Tool works across the ways developers build agents in Microsoft Foundry: Prompt agents provide the fastest way to create a browser-enabled agent by configuring its instructions, model, and tools. Hosted...

Amazon Braket is now in scope for FedRAMP Class C in AWS US Regions where Braket is available. The Federal Risk and Authorization Management Program (FedRAMP) is a US government-wide program that delivers a standard approach to the security assessment, authorization, and continuous monitoring of cloud products and services. With FedRAMP Class C authorization, government customers and the organizations that serve them can use Amazon Braket to explore quantum computing within an authorized boundary. The AWS-operated components of Braket, including the API and SDK, job orchestration and management, compilation, and result storage in Amazon S3, are within the FedRAMP-certified boundary, while quantum workloads execute on third-party Quantum Hardware Providers (QHPs) outside that boundary. All data sent to QHPs meets AWS' privacy and security requirements including removal of all personally identifiable information, data encryption in transit and at rest, and adherence to AWS' stan...

Wrapping up our quick introduction to the C++ futures library , we come to the last two parts: std:: future and std:: shared_future . The std:: future is the starting point. It is a move-only class that this takes the source and forwards its wait and wait_for methods to the source , and forwards its get method to consume . Forwarding the get to consume means that you can call get only once. The idea is that std:: future is for the case where there is exactly one consumer of the value. Since it is move-only, you can't copy it; you can only give it away and transfer the power to retrieve the value to the recipient. The std:: future has a method called shared() . This transfers the source from the future to a shared_ future object. The shared_ future also forwards its wait and wait_for methods to the source , but instead of forwarding its get to the source:: consume , shared_ future:: get() just calls source:: get to get a reference to the value storage. This...

Oracle Database@AWS (ODB) now supports advertising aggregate routes and a default route (0.0.0.0/0) when configuring ODB peering between applications in an Amazon VPC and databases in an ODB network. This simplifies network operations as customers extend new VPCs or on-premises networks to reach their databases, without updating the advertised CIDRs for each network that needs connectivity to the ODB network. Previously, customers had to advertise each network reaching the ODB network as a separate CIDR, and could not advertise a broad aggregate range or a default route. With this launch, customers can advertise any CIDR range, so a single aggregate or default route can cover all networks reachable through the peered VPC, such as those connected through an AWS Transit Gateway, without a separate entry for each one. This capability is available on ODB networks that support multiple ODB peering connections, in all AWS Regions where Oracle Database@AWS is available. To learn more, visit...