Regarding the Cisco Support cutover from AppDynamics Support:   I have been an AppDynamics Admin for over 6+ years, and it surprises me that when I log in to the Account Support page it shows my account information, account name, url to my controller and Entitlements, all account contacts, and wow, all automagically. But, when I attempt open a support ticket Cisco forgets who I am!  Really?    I get a colored/lavender highlighted message:   How is this possible, and why?   This was a poor design choice in how to handle the Support cutover to Cisco Support and should not be the long time AppDynamics users responsibility to fix.  It should have been x-ref'ed during setup or importation into Cisco support from AppD support.  This is someone taking a shortcut, and assigning me work to fix what they should have done to begin with.   Why? SOLUTION: Consider having a programmer in Cisco support create some shim code to run while a user opens the Cisco Support Web page, query does user have AppDynamics Entitlement associated in their Profile? if no, Are they attached to/associated with https://accounts.appdynamics.com/? (in the database, which opens the users AppD info like mine does), if yes, ask the user "Is Account Name (presenting the one the user is associated with in accounts.appdynamics.com) the Entitlement which should be attached to your profile?", if answer is yes, (validate) does users email address match Owners/Company's email domain, if yes, request Account Owner to approve requester be added to the account Entitlement. Or have the Cisco Account manager/ Customer Success Manager approve the user to complete the profile.  Or vibe code it, use AI? So this is a complaint, but it is a complaint with a solution.    The key point is that this issue is not one that requires customer support from my side. The actions required to resolve this matter fall within your area of responsibility and should not be reassigned to me. I have already identified the issue and provided a viable solution for moving forward. At this stage, you have the necessary information, resources, and authority to act. The next steps are in your hands, and I would ask that you proceed accordingly. Poor design decisions chase users from Customer support, it does not provide it.   ... View more