Rename Azure Subscription
complete
R
Rebecca
As an application team I need to adjust the names of my project and Azure Subscriptions to align with new naming patterns within my organization.
This can happen whenever there is an organizational change. If the names don't follow the new naming concept I run into compliance issues.
At the moment I am able to change the project name but this does not lead to an automatic update on the subscription name. I am also not allowed to change the subscription name manually.
There is also no warning that a change of the project name will not be reflected in the subscription name which leads to further confusion.
J
Johannes Rudolph
marked this post as
complete
Update: Configurable Enforcement of Azure Subscription Name Pattern now available
With meshStack v2025.54.0, you can now enforce Azure subscription name patterns updates. If you need to change identifiers for a tenant, we recommend moving it to a different project using the self-service "Move Tenant" feature available in the admin area. We do not plan to support updating display names to include project display names configured in meshStack.
What's available now:
*
Enforce Naming Patterns:
meshStack can now update Azure subscription display names to match your configured naming pattern.*
Correction of Drifts:
Ensures subscription names stay in sync even after initial provisioning.*
Configurable:
This behavior is optional and can be enabled per platform.Pre-requisites:
* Enable the "Update Subscription Name" option in your Azure platform configuration.
* Ensure your meshStack service principal has the
Microsoft.Subscription/rename/action
permission.As we think the move tenant functionality covers this use case combined with the automated correction of naming drifts shipped in this release, we consider this request as solved. We look forward to your feedback.
R
Rebecca
While we currently don’t offer this feature, we are planning on offering it or something similar to it in the future. I can’t give an exact timeline of when it will be ready but I can propose a workaround.
Workaround: Adapt the e.g. subscription name pattern to tags instead of identifiers. Project and workspace identifiers are immutable at the moment and can not be changed. When you want to have the flexibility to change the name of a subscription, project and workspace it is best to work with tags to make up the subscription. The naming patterns can be changed in the platform configuration under replication behavior.