Announcing initial 1.0 release of my include-file crate with #rustlang macros that effectively let you hide setup code in plain markdown files (md, adoc, etc.) like you can in doctests. We use these in some #AzureSDK docs to keep samples focused while still making sure they compile and work.
Azure SDK Release (March 2026)
buff.ly/ddbUf83
#azure #cloud #azuresdk #webdev #dotnet #java #javascript #python #golang
Pot of chili with lid tied down for transport and the last competition’s trophy for first place: a wooden spoon in a vase that reads, “Azure SDK Chili Cookoff 2024”. The knot is a nice trucker’s hitch tied to a bowline with a progress-capturing loop.
Onions browning in a blend of secret ingredients in a pan on a stove.
Bunch of cans of beans and tomato sauce with red peppers, green peppers, and a yellow onion on a countertop.
Can I retain first place for my vegetarian chili in the #AzureSDK team? We’ll find out today.
Azure Developer CLI (azd): One command to swap Azure App Service slots
buff.ly/5FHt9im
#azure #azd #cloud #cli #azuresdk #appservice #commandline
Made it really easy to install the azsdk-samples MCP to add #AzureSDK samples as context: install it into #CopilotCLI as a plugin: copilot plugin install heaths/azsdk-samples-mcp
The MCP makes a significant improvement, especially for #rustlang, when using the Azure SDK libraries.
Azure SDK Release (February 2026)
buff.ly/fgjKEN3
#azure #cloud #foundry #azuresdk #dotnet #python #golang #java #javascript
Azure Developer CLI (azd) – February 2026: JMESPath Queries & Deployment Slots
buff.ly/IMP2ZPP
#azure #cloud #azd #azuresdk #cli #commandline #terminal
What’s new in Microsoft Foundry | Dec 2025 & Jan 2026 | by Nick Brady
ift.tt/kuiqREP
#ai #azure #foundry #agents #models #microsoftfoundry #azuresdk
We've been prototyping polymorphic models for #AzureSDK as enums (DUs) in #rustlang. Endpoints may take a Dog but also might take a Lab so we need distinct types. Tuple variants make sense. It means defining the discriminator in the struct as well, though, but we made serde work. Thoughts on DX?
Azure SDK Release (January 2026)
buff.ly/pDd5bJk
#azure #cloud #ai #foundry #dotnet #golang #python #java #javascript #typescript #azuresdk
non_exhaustive alone prevents literal construction - in the same reference doc: doc.rust-lang.org/reference/at...
We had this for a while in #AzureSDK for #rustlang but found it to cause more friction than worth it to. When all your data fields are pub anyway, forcing a constructor is pointless.
I started a little side project to improve code generation by adding #AzureSDK samples as context. With LLMs trained on older, possibly outdated APIs, this makes a significant difference as my demo shows.
Even once LLMs catch up to our upcoming GA #rustlang APIs this can still help discoverability.
Azure SDK Release (November 2025)
buff.ly/xXURdcY
#azure #azuresdk #dotnet #java #javascript #python #golang #azd
Foundry Local comes to Android—plus on-device speech, on-prem support, and a simpler SDK
ift.tt/yZ8O3qF
#azure #foundrylocal #android #ai #mobiledev #aimodels #azuresdk
Announcing the azd AI agent extension: Publish Microsoft Foundry agents directly from your development environment
buff.ly/kXmWilF
#azure #azd #azuresdk #microsoftfoundry #ai #aiagents #foundry
*) We created the original #AzureSDK for #dotnet snippet generator because, at one point, the Key Vault README examples wouldn't even compile nonetheless work. They were based on older code, and we wanted someway to make sure they were always accurate.
Do people think the old docs or the new docs look better?
Old: github.com/Azure/azure-...
New: github.com/Azure/azure-...
The code to create a SecretClient in #rustlang is a little higher up in the README. This mirrors what most other #AzureSDK languages do while allowing us to compile snippets.
New #AzureSDK for #rustlang!
This is our "breakiest" change yet. Since we're in the home stretch and after a cross-language review, we've made a few API changes like into_body() -> into_model() but we still define `into_body(self) -> ResponseBody`, congruent with `AsyncResponse`.
The `include-file!()` macro is effective the inverse of what I cowrote before for #dotnet but possibly for use in #AzureSDK for #rustlang. We can put just the code we want to show in markdown but still test that it compiles or even runs. Better than our current pattern: github.com/Azure/azure-... ?
Many years back, another dev and I implemented testable code snippets for #AzureSDK for #dotnet. Prior, nothing verified that code in markdown would work or even compile. Doc tests in #rustlang are great, but you can't hide setup code in plain markdown...until now.
Channel9 Building Secure Applications with Azure and Rust | DEM511: Learn how the Azure SDK for Rust helps you build secure, memory-safe, and high-performance cloud applications. This session will showcase practical use cases, like managing secrets with… #AzureSDK #RustProgramming #CloudSecurity
Introducing the azd extension to configure GitHub Copilot coding agent integration with Azure
buff.ly/fEBnwva
#azure #cloud #githubcopilot #azd #cli #aiagents #ai #azuresdk
Azure SDK Release (October 2025)
buff.ly/MgdKuXB
#azure #cloud #azuresdk #dotnet #javascript #python
Yeah, I’m happy with the new long-running operation (LRO) API experience I finished: returns a Poller that implements IntoFuture to just wait for it to complete and get the result on success - as in most #AzureSDK languages - and Stream to manually poll the status if that’s your jam.
Azure Developer CLI (azd) – October 2025
buff.ly/GC7P5o9
#azure #cli #azd #cloud #webdev #commandline #azuresdk
![Screenshot of `akv --help` reading:
The Azure Key Vault CLI (unofficial) can read secrets from Key Vault,
securely pass secrets to other commands or inject them into configuration files,
encrypt and decrypt secrets, and managed keys and secrets in Key Vault.
Usage: akv [OPTIONS] <COMMAND>
Commands:
inject Inject secrets from Azure Key Vault into a templated file or input between {{ }}
run Pass secrets in environment variables to a process
read Read a secret from Azure Key Vault
encrypt Encrypt content to a compact JSON Web Encryption (JWE) token
decrypt Decrypt a compact JSON Web Encryption (JWE) token
secret Manage secrets in Azure Key Vault
key Manage keys in Azure Key Vault
certificate Manage certificates in Azure Key Vault
completion Generates completion scripts for supported shells
help Print this message or the help of the given subcommand(s)
Options:
-c, --color <COLOR> Print colors [default: auto] [possible values: auto, always, never]
-v, --verbose... Log verbose messages. Pass `-vv` to log more verbosely
-h, --help Print help
-V, --version Print version](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:tg3tb5wukiml4xmxml6qm637/bafkreigjjj6h4sfjqy4r2m47ju3hdwmydi2v7ltkd2nw3m2bq3nbbtcfti)
Screenshot of `akv --help` reading: The Azure Key Vault CLI (unofficial) can read secrets from Key Vault, securely pass secrets to other commands or inject them into configuration files, encrypt and decrypt secrets, and managed keys and secrets in Key Vault. Usage: akv [OPTIONS] <COMMAND> Commands: inject Inject secrets from Azure Key Vault into a templated file or input between {{ }} run Pass secrets in environment variables to a process read Read a secret from Azure Key Vault encrypt Encrypt content to a compact JSON Web Encryption (JWE) token decrypt Decrypt a compact JSON Web Encryption (JWE) token secret Manage secrets in Azure Key Vault key Manage keys in Azure Key Vault certificate Manage certificates in Azure Key Vault completion Generates completion scripts for supported shells help Print this message or the help of the given subcommand(s) Options: -c, --color <COLOR> Print colors [default: auto] [possible values: auto, always, never] -v, --verbose... Log verbose messages. Pass `-vv` to log more verbosely -h, --help Print help -V, --version Print version
New version of the (unofficial) Azure Key Vault CLI (akv) available on #homebrew or from github.com/heaths/akv-c...
This version adds key and certificate management, along with updates to use the latest #AzureSDK for #rustlang crates we're getting close to GA'ing.
New versions of azure_core and its dependencies have been released. We’ll be releasing updated #AzureSDK for #rustlang crates built on it next week.
This also includes our new cloud configuration API that will help azure_identity and eventually other Azure SDK crates that need it (uncommon).
The amount of churn in this PR within the #AzureSDK for #rustlang repo is fairly large but should be a small change for callers: just get rid of the `.await` after `into_body()` in nearly all cases.
This is congruent with other Azure SDK languages as well.
Screenshot of Rust code that reads, let secret = secret_client .get_secret("secret-name", None) .await? .into_body()?; // .await? no more println!("{}", secret.value.unwrap_or_default());
Small change the size of a large change coming to #AzureSDK for #rustlang: while all client methods continue to be async, deserializing models is now sync. In most cases we already buffered the entire response anyway, but the goal was making sure we do so entirely in the pipeline (policy chain).
