Summary
The ability to bypass tag validation when creating or updating meshObjects via API with admin permissions is being deprecated and will be removed on
April 1, 2026
.
Background
Previously, principals with admin permissions could create or update meshObjects with invalid tags via the meshObject API, bypassing validation of tags against configured tag definitions. This was originally allowed to simplify importing data from external systems. However, many meshStacks are now used by multiple platform teams and this flexibility can create inconsistencies in tagging.
Since Tag validation via API changes was explicitly requested as a feature here before, we are now making tag validation the default behavior and will deprecate the bypass option for admin permissions.
Affected meshObject Types
All meshObject types that support tags when created or updated with admin permissions:
  • meshWorkspaces
  • meshProjects
  • meshBuildingBlockDefinitions
  • meshPaymentMethods
  • meshLandingZones
  • meshProjectRoles
Please review your API integrations that create or update these meshObjects with admin permissions to ensure future compliance with tag validation.
Any API use that uses only workspace-scoped permissions is not affected by this change and will continue to enforce tag validation as before.
Timeline
  • ✅ October 29, 2025
    : Initial rollout of tag validation for meshWorkspaces and meshProjects (Release 2025.47.0).
  • November 19, 2025
    : Rollout of tag validation to all meshObject types. The legacy tag validation bypass behavior is available as an option in the Admin Area settings.
  • ⚠️ April 1, 2026
    :
    MANDATORY - All meshStack instances must enforce tag validation
NOTE: 2025.47.0 defaulted to enabling tag validation, when the setting was not explicitly configured. In order to minimize any disruptions, we have decided to default to the legacy bypass behavior until April 1, 2026, unless explicitly configured. This change will be made available Nov 19th.
Required Actions
Before April 1, 2026, you must:
  1. Review your API integrations
    that create or update meshObjects with admin permissions
  2. Ensure all tag values comply
    with your configured tag catalog
  3. Update your integrations
    if they currently rely on bypassing validation
  4. Test your changes
    before the mandatory rollout date by deactivating the tag validation bypass in your meshStack settings
If you do not take action, API calls that create or update meshObjects with invalid tags using admin permissions may start to fail after April 1, 2026.
If you have disabled the legacy tag validation bypass in your meshStack settings, there is no further action required.
Changing Tag Validation Settings
You can enable the new tag validation behavior to test your integrations:
  1. Navigate to
    Admin Area → Settings → Compliance → Tags
  2. Toggle off "Enable Legacy Tag Validation Bypass for meshObject API"
Resources
Need Help?
If you need assistance updating your integrations or have questions about this change, please contact our customer success team or reach out to support at support@meshcloud.io