Samuel Liew: I thought the way I answered was implicit enough.
The following is the same expanded to be more explicit:
Sean: Unclear from the above if you got an answer or you solved it yourself.
As, I can't see an answer and your last comment suggests you went off with false information.
Certainly your code should work in 2010 office systems.
I'm doing just that and activating a range of different tabs, based on targeted worksheet 'types' becoming active. And the tab activation code is just part of a general workbook events handling sub (i.e. called by application event handlers).
And that has been operational since prior to you asking this question.
So the response from Siddharth Rout above about not being able to do this is invalid.
I'm assuming your Tab id is defined in the xml to match the id in your code above per:
<tab id="Configure" label="YOUR LABEL" >
I'm also assuming the rest of your xml is correct, and you can see the tab, just not be able to activate it.
If all that's the case, as to 'How to': You should just need to call that sub.
In my case I do that on Workbook or Worksheet activated (on open or change of window). But any call mechanic (such as your in-sheet control) should work just as well.
As an aside, I'd recommend using more obviously unique codes for ribbon control ids
e.g. Using some leading chars from the overall function and the control type like 'xyzTab_Configure'.
Just means if/when you add more, you have a explicit way to know which is which, and avoid any clashes.
That all covered: I have however run into an issue with office 2019.
See: vba IRibbonUI.ActivateTab not working in Office 2019