diff --git a/docs/features/techdocs/extensions.md b/docs/features/techdocs/extensions.md
new file mode 100644
index 0000000000..6c69d076a4
--- /dev/null
+++ b/docs/features/techdocs/extensions.md
@@ -0,0 +1,62 @@
+---
+id: extensions
+title: Using TechDocs Extensions
+sidebar_label: Using TechDocs Extensions
+description: How to use the built-in TechDocs extension points
+---
+
+# TechDocs Backend Extensions
+
+The TechDocs backend plugin provides the following extension points:
+
+- `techdocsPreparerExtensionPoint`
+  - Register a custom docs [PreparerBase extension](https://backstage.io/docs/reference/plugin-techdocs-node.preparerbase/)
+  - Ideal for when you want a custom type of docs created for a specific entity type
+- `techdocsBuildsExtensionPoint`
+  - Allows overriding the build phase Winston log transport (by default does not log to console)
+  - Allows overriding the [DocsBuildStrategy](https://backstage.io/docs/reference/plugin-techdocs-node.docsbuildstrategy/)
+- `techdocsPublisherExtensionPoint`
+  - Register a custom docs publisher
+- `techdocsGeneratorExtensionPoint`
+  - Register a custom [TechdocsGenerator](https://backstage.io/docs/reference/plugin-techdocs-node.techdocsgenerator/)
+
+Extension points are exported from `@backstage/plugin-techdocs-backend`.
+
+## Examples
+
+### Log TechDocs Build phase details to console
+
+By default, the TechDocs build phase logs to the UI, but does not log to the console. However, the
+`techdocsBuildsExtensionPoint` can be used to setup a custom Winston transport for TechDocs build logs.
+
+Here is an example of logging to console:
+
+```typescript jsx title="packages/backend/src/extensions/techDocsExtension.ts"
+import { techdocsBuildsExtensionPoint } from '@backstage/plugin-techdocs-backend';
+import { createBackendModule } from '@backstage/backend-plugin-api';
+import { transports } from 'winston';
+
+export const techDocsExtension = createBackendModule({
+  pluginId: 'techdocs',
+  moduleId: 'techdocs-build-log-transport-extension',
+  register(env) {
+    env.registerInit({
+      deps: {
+        build: techdocsBuildsExtensionPoint,
+      },
+      async init({ build }) {
+        // You can obviously use any custom transport here...
+        build.setBuildLogTransport(new transports.Console());
+      },
+    });
+  },
+});
+```
+
+And then of course register this extension with the backend:
+
+```typescript jsx title="packages/backend/src/index.ts"
+import {techDocsExtension} from "./extensions/techDocsExtension";
+...
+backend.add(techDocsExtension);
+```
diff --git a/microsite/sidebars.js b/microsite/sidebars.js
index 9525141073..871cec0a0f 100644
--- a/microsite/sidebars.js
+++ b/microsite/sidebars.js
@@ -116,6 +116,7 @@ module.exports = {
           'features/techdocs/concepts',
           'features/techdocs/addons',
           'features/techdocs/architecture',
+          'features/techdocs/extensions',
           'features/techdocs/creating-and-publishing',
           'features/techdocs/configuration',
           'features/techdocs/using-cloud-storage',
diff --git a/mkdocs.yml b/mkdocs.yml
index b2d0a5489d..aa545111d4 100644
--- a/mkdocs.yml
+++ b/mkdocs.yml
@@ -85,6 +85,7 @@ nav:
           - Configuring CI/CD to generate and publish TechDocs sites: 'features/techdocs/configuring-ci-cd.md'
           - CLI: 'features/techdocs/cli.md'
           - HOW TO guides: 'features/techdocs/how-to-guides.md'
+          - Extensions: 'features/techdocs/extensions.md'
           - Troubleshooting: 'features/techdocs/troubleshooting.md'
           - FAQ: 'features/techdocs/FAQ.md'
   - Integrations: