<!-- Please complete the template below as best as you can. Make sure to check if this issue has already been raised by someone else first to avoid duplication. For each section below, please add screenshots or links or anything that may help visual learners understand the problem better, even if this takes you an extra minute or two this is a great help to some folks. https://www.learning-styles-online.com/style/visual-spatial/ --> ### Problem Providing feedback on the process to request an internal dedicated license/renewal ### Feedback **Overall timeline:** - Joined dedicated office hours, was directed to reach out to support to see how they approached their renewal - Reached out to support and was directed to this thread that seemed to just be extra steps to request a license: https://gitlab.slack.com/archives/C018C623KBJ/p1741617033391639 - Decided to reach out in g_provision for assistance, resulted in personal confusion over the wide range of same name licenses currently used on dedicated - Temporarily directed to reach out back in the dedicated slack channels and pointed to a similar issue - Dedicated team responded to my repeat question that I was able to apply the license myself (this was not clear as so much of dedicated has to go through their request process) - End result was a chat in the provision channel where we decided to just have a license renewal that I can apply myself **Takeaways/Pain points** - No standard request path, throughout my asks learned that licenses for dedicated instances had been acquired in 3 different ways (including the current approach) - Felt that the dedicated team was unsure about how to apply/request the new license - Request path itself involved a few too many tasks: joining calls, sending messages, responding on issues - feels like a standard issue request linked from the docs could be an easy solve <!-- Consult with `@gitlab-com/business-technology/enterprise-apps/zuora-architects` on the ~"Enterprise Applications" team if Zuora business logic is involved. -->