aah - sorry - if I understand correctly that I dont have - the instructions make the assumption you ALREADY have a VSTS project setup ready for your SoapUI projects and that you've made all the pre-amble alterations to your SoapUI Project before starting with those instructions.
You need to create a project within VSTS to point to.
I don't know how to do this I'm afraid - the DevOps people where I worked own VSTS so they created my project for me.
HOWEVER - I would suggest there have got to be some instructions published for creating a new project in VSTS. I don't have permissions myself to create a project in our VSTS - so I can't do it myself and provide the actions to do this - but it shouldn't be too difficult.
I'd suggest googling "create a project in VSTS" and go from there. Sorry I couldn't be of more help - but once you have the VSTS project and you've updated your SoapUI Project and converted to 'composite' option (as well as selecting the prettyprint wsdl preference) - the instructions I provided will give you everything else you need.
when you say "take care of the bearer token"... can you rephrase the question please? unless the place where your repo resides has different topological attributes (i "think" thats the corrwct term..??) so the security settings would be different to enable access to the soapui project, if im understanding the question correctly it shouldnt make any difference. however im guessing at what youre question actually is, so could do with an explanation just to be sure!
What I meant was that do we need to take care of any authentication related stuff as well in SOAPUI testing. In my project they use bearer token as a authentication mechanism which expires every hour. So do we need to take care of those things while integrating SOAPUI in VSTS or providing the project as .xml file in VSTS is enough to complete the build.