Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request]: Set a custom 'friendly name' for tenants within the CIPP GUI #2018

Closed
LachlanBenson opened this issue Jan 16, 2024 · 1 comment
Labels
enhancement New feature or request no-priority

Comments

@LachlanBenson
Copy link

Description of the new feature - must be an in-depth explanation of the feature you want, reasoning why, and the added benefits for MSPs as a whole.

Feature Description: Can set a custom or 'friendly' name for an M365 tenant. This friendly name should be viewable under the tenant administration screen such as shown below.
image

Also, it should be viewable in the select tenant dropdown list.
image

As an MSP, we manage hundreds of client tenants. Some of our clients are known by various entity names and our clients often have different names within our PSA tool (ConnectWise in our case) to the names of their M365 tenants. We would like a custom field to be created that allows a Custom "Friendly name" to be set for each TenantID, to allow for ease of searchability in the event that a client can be known by multiple names, or where their M365 tenant does not match up to the name within our PSA tool.

PowerShell commands you would normally use to achieve above request

N/A

@LachlanBenson LachlanBenson added enhancement New feature or request no-priority labels Jan 16, 2024
@KelvinTegelaar
Copy link
Owner

Not going to be implemented. You can change the display name of tenants via the edit tenant functionality, that only impacts your partner center side and not the client.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request no-priority
Projects
None yet
Development

No branches or pull requests

2 participants