diff --git a/src/csharp/BUILD-INTEGRATION.md b/src/csharp/BUILD-INTEGRATION.md
index 237a63a430d..4f2f57cfcdc 100644
--- a/src/csharp/BUILD-INTEGRATION.md
+++ b/src/csharp/BUILD-INTEGRATION.md
@@ -36,6 +36,9 @@ Support is provided for the following platforms:
 * MacOS (x64 and arm64 via using the x64 binaries)
 * Linux (x86, x64, and arm64)
 
+You may still use the MSBuild integration provided by `Grpc.Tools` for other architectures provided you can supply the codegen binaries for that platform/architecture.
+See [Using Grpc.Tools with unsupported architectures](#unsupported-arch) below.
+
 ## Adding `.proto` files to a project
 
 To add `.proto` files to a project edit the project’s `.csproj` file and add an item group with a `<Protobuf>` element that refers to the `.proto` file, e.g.
@@ -227,6 +230,7 @@ Quick links to the examples below:
 * [Generate proto and gRPC C# sources from .proto files (no C# compile)](#nocompile)
 * [Visual Studio: setting per-file `.proto` file options](#visualstudio)
 * [Bypassing Grpc.Tools to run the protocol buffers compiler explicitly](#compiler)
+* [Using Grpc.Tools with unsupported architectures](#unsupported-arch)
 
 ---
 ## <a name="ProtoRoot"></a>ProtoRoot - Common root for one or more `.proto` files
@@ -487,6 +491,59 @@ Do not include any `<Protobuf>` items in the project file as that will invoke th
 
 ---
 
+## <a name="unsupported-arch"></a>Using Grpc.Tools with unsupported architectures
+
+You may still use the MSBuild integration provided by `Grpc.Tools` for architectures where
+the binaries are not included in the `Grpc.Tools` NuGet package.
+
+If you are able to build your own binaries for `protoc` and `grpc_csharp_plugin`, or
+find pre-built binaries provided by the community, then you can define a couple of
+environment variables to tell `Grpc.Tools` to use those binaries instead of the ones
+provided in the NuGet package:
+* `PROTOBUF_PROTOC`  - Full path to the protocol buffers compiler
+* `GRPC_PROTOC_PLUGIN` - Full path to the `grpc_csharp_plugin`
+
+Things to note:
+*  You need `Grpc.Tools` version 2.50.0 or later for these environment variables to
+be recognised.
+
+* The binaries bundled in `Grpc.Tools` already ensure that the correct and mutually
+compatible version of `protoc` and `grpc_csharp_plugin` will be chosen, but when
+providing them yourself, you're in charge.
+
+* If the versions of `protoc` and `grpc_csharp_plugin` you provide are mutually
+incompatible then code generated may not work with your application (e.g. breaks
+the build).
+
+* Specifically, older version of plugins may generate incompatible code
+or may not contain patches/fixes.
+
+_An example for Alpine Linux_
+
+For Alpine Linux (which uses the *musl* C standard library) there are community
+provided packages for the protocol buffers compiler and gRPC plugins:
+[https://pkgs.alpinelinux.org/packages?name=grpc-plugins](https://pkgs.alpinelinux.org/packages?name=grpc-plugins)
+
+To use these:
+```bash
+# Build or install the binaries for your architecture.
+
+# e.g. for Alpine Linux the grpc-plugins package can be used
+#  See https://pkgs.alpinelinux.org/package/edge/community/x86_64/grpc-plugins
+apk add grpc-plugins  # Alpine Linux specific package installer
+
+# Set environment variables for the built/installed protoc
+# and grpc_csharp_plugin binaries
+export PROTOBUF_PROTOC=/usr/bin/protoc
+export GRPC_PROTOC_PLUGIN=/usr/bin/grpc_csharp_plugin
+
+# When the dotnet build runs the Grpc.Tools NuGet package will
+# use the binaries pointed to by the environment variables
+dotnet build
+```
+
+---
+
 ## See also
 
 gRPC project documentation: