News For Dev-ops

Today, AWS announces the general availability of Organizational Notification Configurations for AWS User Notifications. This launch allows AWS Organizations users to centrally configure and view notifications across their organization. You can use the Management Account or Delegated Administrators (DAs) to configure and view notifications about accounts included in specific organizational units (OUs) or all accounts rolling up to an organization. Once configured, events from any of the member accounts will generate a notification in the Management Account. User Notifications supports up to 5 DAs. You can use this capability to setup notifications for any supported Amazon EventBridge Event . For example, you can setup a notification configuration to send a push notification to the AWS Console Mobile Application anytime a user in any of the member accounts in your organization signs in to the console without MFA. Notifications will also be available in the Admin’s Console Notification...

AWS Control Tower and Control Catalog APIs now allow customers to use Internet Protocol version 6 (IPv6) addresses. With the new dual-stack endpoints, customers can connect to AWS Control Tower and over the public internet using IPv6, IPv4, or dual-stack clients. The existing AWS Control Tower endpoints supporting IPv4 will remain available for backwards compatibility. The continued growth of the Internet, particularly in the areas of mobile applications, connected devices, and IoT, has spurred an industry-wide move to IPv6. IPv6 increases the number of available addresses by several orders of magnitude so customers will no longer need to manage overlapping address spaces in their Amazon Virtual Private Cloud (Amazon VPC). Support for IPv6 on AWS Control Tower and Control Catalog API is available in all Regions where AWS Control Tower and Control Catalog API are available. For a full list of Regions where AWS Control Tower is available, see the  AWS Region Table . To learn more...

A colleague was investigating a crash. The stack at the point of the crash looks like this: contoso!winrt::impl::consume_Windows_Foundation_Collections_IVectorView< winrt::Windows::Foundation::Collections::IVectorView<int>, int>::Size+0x30 contoso!winrt::Contoso::implementation::Widget:: InitializeNodesAsync$_ResumeCoro$1+0x2bc contoso!wil::details::coro::apartment_resumer::resume_apartment_callback+0x28 combase!CRemoteUnknown::DoCallback+0x34 combase!CRemoteUnknown::DoNonreentrantCallback+0x48 rpcrt4!Invoke+0x64 rpcrt4!InvokeHelper+0x130 rpcrt4!Ndr64StubWorker+0x6cc rpcrt4!NdrStubCall3+0xdc combase!CStdStubBuffer_Invoke+0x6c combase!ObjectMethodExceptionHandlingAction<⟦...⟧>+0x48 combase!DefaultStubInvoke+0x2b8 combase!SyncServerCall::StubInvoke+0x40 combase!StubInvoke+0x170 combase!ServerCall::ContextInvoke+0x3c4 combase!ReentrantSTAInvokeInApartment+0x1fc combase!ComInvokeWithLockAndIPID+0xcc4 combase!ThreadDispatch+0x514 combas...

This blog post summarizes changes to the vcpkg package manager as part of the 2025.08.27 registry release as well as changes to vcpkg documentation throughout August. There were no tool changes as of the date of the registry release in August, though more changes will be listed in the next release in September. Some stats for this period: There are now 2,666 total ports available in the vcpkg curated registry. A port is a versioned recipe for building a package from source, such as a C or C++ library. 14 new ports were added to the curated registry. 240 ports were updated . As always, we validate each change to a port by building all other ports that depend on or are depended by the library that is being updated for our 15 main triplets . 86 community contributors made commits. The main vcpkg repo has over 7,000 forks and 25,500 stars on GitHub. GitHub Dependabot support for vcpkg Earlier this month, we announced GitHub Dependabot support for vcpkg . This allows GitHub...

Ever found yourself staring at the Output Window, overwhelmed by endless lines of logs and cryptic messages?  You're not alone! For years, developers have relied on the Output Window for critical build and debug information. But making sense of it—and translating it into action—has been a challenge. What if you could instantly ask questions about your logs and take action without leaving your workflow? Now you can, thanks to Copilot’s new Output Window context !   Say hello to smarter output window assistance In Visual Studio 17.14, Copilot can now read your Output Window, making it possible to interact with your build and debug logs like never before. Instead of wading through log files and searching for answers, simply ask Copilot questions about the output—whether you’re facing build errors, warnings, or just want to understand what’s happening behind the scenes.   How does the Output Window context work?   If ...

Delivering high-quality software is a necessity and that’s why Azure Test Plans has introduced the all-new Test Run Hub , an enabler for teams who want to take control of their testing process and drive continuous improvement. What Makes the Test Run Hub a Must-Have? The Test Run Hub is designed to help teams track test progress, analyze results, and maintain quality across every development cycle. Whether you’re running manual or automated tests, the new test run hub brings clarity and efficiency to your quality assurance workflow. Key Benefits Real-Time Visibility: Instantly monitor test progress and quality trends, so you can spot regressions or failures before they impact your release. Comprehensive Analytics: Dive into historical test data to audit, analyze, and continuously improve your testing strategy. Seamless end to end user flow: Test runs are created automatically from test plans or automated test pipelines, capturing every detail of an execution's outcomes. ...

We're excited to announce the release of Dev Proxy v1.1. This update delivers critical fixes for Microsoft Graph batch request simulation, resolves authentication plugin issues, and enhances the MinimalPermissionsGuidancePlugin with new reporting capabilities. In this version: Fixed Microsoft Graph batch response handling Resolved authentication plugin initialization issues Enhanced MinimalPermissionsGuidancePlugin with markdown and text reports Added scope filtering for permissions guidance Performance optimizations for MSGraphDb generation Fixed Microsoft Graph batch response handling We've addressed a critical issue where the GraphRandomErrorPlugin incorrectly returned HTTP status code 424 instead of 200  for Microsoft Graph batch requests containing failed individual requests. What changed: Batch responses now correctly return HTTP 200 OK as per Microsoft Graph specifications Individual requests within batches maintain their proper error codes (e.g., 429 for t...

A new release of the Microsoft build of Go including security fixes is now available for download . For more information about this release and the changes included, see the table below: Microsoft Release Upstream Tag v1.25.1-1 go1.25.1 release notes v1.24.7-1 go1.24.7 release notes Post Updated on September 04, 2025 at 04:32AM Thanks for reading from devamazonaws.blogspot.com

TL;DR Models : GPT‑5 family now in Azure AI Foundry (gpt‑5 requires registration; launch regions: East US 2, Sweden Central). Also new: Sora API updates (image→video, inpainting; Global Standard in East US 2 and Sweden Central), Mistral Document AI (OCR), Black Forest Labs FLUX.1 Kontext [pro] and FLUX1.1 [pro], OpenAI gpt‑oss (with Foundry Local support), and VibeVoice long‑form TTS (coming soon). Agents : Browser Automation tool (public preview) and expanded Agent Service regional availability (Brazil South, Germany West Central, Italy North, South Central US). Tools : Browser Automation integrates with Microsoft Playwright Testing Workspaces; refreshed MCP samples; updated Deep Research guidance and samples. Platform : Model Router adds GPT‑5 support (limited access); Responses API is GA. August updates across Python, .NET, Java, and JavaScript/TypeScript; Agent Service Java SDK enters public preview. Doc updates include new status dashboard (Preview), API lifecycle v1 guidance, up...

I often get asked about how one could use C++/WinRT's IAsyncOperation<T> where T is not a Windows Runtime type. The T in IAsyncOperation<T> must be a Windows Runtime type because the algorithm for generating an interface ID for IAsyncOperation<T> works only on Windows Runtime types. But all hope is not lost. You just have to decide which rule you want to break. The best solution is to break the rule "I'm using IAsyncOperation<T> ." Instead, use some other coroutine library that supports arbitrary C++ types. Available options include cppcoro::task<T> , wil::task<T> (based on my simple_task , but expanded to support COM via wil:: com_task<T> ), and concurrency::task<T> . Another option is not to use the T to return the result, but rather pass the output parameter as an explicit input. winrt::IAsyncAction DoSomethingAsync(std::shared_ptr<std::optional<Widget>> result) { ⟦ calculations... ⟧ /...

Our team works with customer solutions that integrate AI into data solutions. Some time ago, this post titled Fabric Change the Game: Unleashing the Power of Microsoft Fabric and OpenAI for Dataset Search | Microsoft Fabric Blog | Microsoft Fabric was shared in our Fabric Blog community. It explored how to integrate OpenAI capabilities into Microsoft Fabric and was based on insights from our team’s experience. At that time, Microsoft Fabric didn’t offer a built-in OneLake Files indexer. Now that it does, we revisited the topic to evaluate how these new capabilities streamline dataset discovery and enhance AI integration, drawing from our continued work with customers. In this step-by-step guide, we'll dive into vector search using the OneLake Files indexer. You'll learn how to extract searchable content and metadata from your files to power advanced search experiences. We'll also explore how Microsoft Fabric and OpenAI work together, making it easier to build AI-driven sol...

Today, AWS announces the ability to manage access to AWS Regions and AWS Local Zones from a single place within the AWS Management Console. With this new capability, customers can now efficiently monitor and manage access to AWS Regions and AWS Local Zones globally. AWS Global View enables customers to view resources across multiple Regions in a single console. To get started, customers can find "AWS Global View" in the AWS Management Console and navigate to the Regions and Zones page. The Regions and Zones page displays infrastructure location details, opt-in status, as well as any parent Region relationships, making it easier for customers to manage and monitor their global AWS footprint. This capability is available in all AWS commercial Regions. To learn more, visit the  AWS Global View  documentation, or navigate to the Regions and Zones page  here . Post Updated on September 02, 2025 at 10:00PM

This release is all about quality-of-life improvements — making it easier to find the setting you’re looking for, spot shortcut conflicts, and even adding a new way to move your mouse cursor. Get the update by checking for updates in PowerToys or heading to the release page . Search in Settings PowerToys has grown a lot over the years, and with so many settings it can sometimes be hard to find exactly what you need. That’s why we’ve added a search box in Settings. Search supports fuzzy matching, so you don’t need to type the exact name. Just press Ctrl+F (or click the search box) and start typing. Suggestions show up right in the flyout, and selecting one takes you straight to the right settings page. Got more than five results? Hit the Show all results button to view everything in the full search page. PR: #41285 Shortcut conflicts Ever used a hotkey and had two things happen at once? With so many shortcuts in PowerToys, it’s easy to run into conflicts. Now, shortcuts that are ...