diff --git a/website/content/docs/upgrading/upgrade-to-1.16.x.mdx b/website/content/docs/upgrading/upgrade-to-1.16.x.mdx
index cebefb5320..48dff1dd76 100644
--- a/website/content/docs/upgrading/upgrade-to-1.16.x.mdx
+++ b/website/content/docs/upgrading/upgrade-to-1.16.x.mdx
@@ -63,6 +63,8 @@ plugin process starts with `SOURCE=parent` and Vault reports a conflict for
 
 ## Known issues and workarounds
 
+@include 'known-issues/1_16-jwt_auth_config.mdx'
+
 @include 'known-issues/1_16-ldap_auth_login_anonymous_group_search.mdx'
 
 @include 'known-issues/1_16-ldap_auth_login_missing_entity_alias.mdx'
diff --git a/website/content/partials/known-issues/1_16-jwt_auth_config.mdx b/website/content/partials/known-issues/1_16-jwt_auth_config.mdx
new file mode 100644
index 0000000000..b87191c497
--- /dev/null
+++ b/website/content/partials/known-issues/1_16-jwt_auth_config.mdx
@@ -0,0 +1,16 @@
+### Error configuring the JWT auth method
+
+#### Affected versions
+
+- 1.16.1
+
+#### Issue
+An error will occur when configuring the built-in jwt auth method. This will
+affect new mounts and updates to existing mounts. Existing mounts should not
+encounter an error if no modifications are made.
+
+See this [issue](https://github.com/hashicorp/vault-plugin-auth-jwt/pull/290) for more details.
+
+#### Workaround
+
+Do not attempt to update an existing mount's config. New mounts can run the plugin as an external plugin to avoid the error.