Upload
others
View
10
Download
0
Embed Size (px)
Citation preview
Format: 1 hour Skype call
Attendees: Key Stakeholders from Customer, Partner teams. Solution Architects, Functional and Technical Leads are mandatory.
• VSTS vs Visual Studio 2015
• Customer already has a VSTS account
• Create a VSTS account
• Create a VSTS project
• Create personal access token
• Manage customer/partner users
• User pre-requisite for build environment
• Setup LCS integration with VSTS
• Common VSTS integration errors and resolutions
AGENDA
•
•
•
•
•
•
• Deploying build environment. Hot fixes are released as X++ and performing a
build is required
• Tracking support incidents submitted to Microsoft through Support, as work
items in VSTS.
• Integration of the Business Process Modeler (BPM) library hierarchy into your
VSTS project, as a hierarchy of work items.
• Deploying build environment. Hot fixes are released as X++ and performing a
build is required
• Tracking support incidents submitted to Microsoft through Support, as work
items in VSTS.
• Integration of the Business Process Modeler (BPM) library hierarchy into your
VSTS project, as a hierarchy of work items.
• Code upgrade
https://www.visualstudio.com
https://<customer>.visualstudio.com
• Click on Personal access token
• Click on Add
• Enter a description
• Enter the Expires in (recommendation is to use the max duration of 1 year)
• Select All scopes
• Click Create Token
account for the partner (@customer.com) user against the
customer’s AAD
• Add the partner’s Microsoft account (MSA) to the customer’s AAD.
If partner user has a Visual Studio/MSDN subscription, then it is
recommended to add the MSA account associated with the MSDN
subscription to the customer’s AAD. This frees up the access level used by
this account.
Make sure to set your access in Team Services to "Visual Studio/MSDN
Subscriber".
• Create the partner user (@partner.com) as an external user against customer’s
AAD (limitations in the Notes section)
https://blogs.msdn.microsoft.com/axdevalm/2016/07/08/vsts-integration-errors-and-resolutions
https://blogs.msdn.microsoft.com/winsdk/2016/09/29/visual-studio-team-services-and-microsoft-accounts-vsts-and-msas/