Azure App Service& lt; - & gt; VSTS部署失败（状态代码：500）at& quot;获取更改& quot;步 [英] Azure App Service <--> VSTS Deployments failing (status code: 500) at "Fetching changes" step
问题描述
我最近在我的VSTS帐户上启用了AAD支持，从那时起，没有任何持续部署源在Azure中工作。我很确定会出现某种权限问题，但我无法弄清楚。在Azure门户（新）中，
我得到"失败"状态，获取步骤的日志返回500错误。
当使用Kudu（或控制台），并尝试从site / repository文件夹执行git pull时，我得到更多细节 - 授权失败错误。当我查看.git / config时，我发现有一个个人访问令牌字符串已被分配
作为拉取源URL的一部分，但用户的VSTS帐户中不会出现新的令牌。
当我在VSTS中查看项目时，我确实看到一个与项目关联的新服务挂钩，因此Azure必须正确设置它。
如果我手动创建一个VSTS个人访问令牌，我可以使用它来使用相同的URL模式成功克隆，但是来自非Azure源（例如，我的本地桌面）的git，所以我知道访问令牌框架正在工作;它必须是Azure试图配置场景的
方式。
我尝试在与我的VSTS帐户和AAD目录相同的订阅上创建新的App Services ，然后链接那些。结果是一样的。
我也尝试在旧的Azure门户中设置部署。这导致为帐户创建新的OAuth授权。但是，最终，我遇到了同样的失败。
此时，似乎Azure认为它在我的VSTS帐户中创建了一个新的个人访问令牌，但是新令牌没有似乎很难坚持。
有人有什么建议吗？我在VSTS方面缺少权限问题，或者AAD用户设置或安全性中的某些内容？ Azure中的东西？
您好，
感谢您在此发帖。
VSTS需要与Azure订阅的安全连接，此连接是基于服务主体的，因此您需要AAD支持Azure订阅，并且您需要具有向AAD添加新应用程序的权限拥有管理员
或共同管理员权限。我建议您检查管理员和共同管理员权限，并告诉我们反馈。
请通过以下文档了解更多信息：
http://www.colinsalmcorner.com/ post / continuous-deployment-of-fabric-media-apps-using-vsts-or-tfs
问候，
免责声明：
此响应包含对第三方万维网站点的引用。 Microsoft提供此信息是为了方便您。 Microsoft不控制这些网站，也未测试在这些网站上找到的任何软件或信息;因此，
Microsoft不能就其中发现的任何软件或信息的质量，安全性或适用性做出任何陈述。使用互联网上的任何软件都存在固有的危险，微软提醒您在从互联网上检索任何软件之前确保您完全了解风险。
I recently enabled AAD backing on my VSTS account, and since then, none of the Continuous Deployment sources have been working in Azure. I'm fairly sure there is some sort of permissions issue going on, but I can't figure it out. In the Azure portal (new), I get "Failed" status, with the log for the fetch step returning a 500 error.
When using Kudu (or the console), and try to perform a git pull from the site/repository folder, I get a little more detail--an Authorization failed error. When I look at the .git/config, I see that there's a personal access token string that's been assigned as part of the pull source URL, but no new tokens appear in the user's VSTS account.
When I look at the project in VSTS, I do see a new Service Hook associated with the project, so Azure must have properly set up that.
If I manually create a VSTS personal access token, I can use that to successfully clone using the same URL pattern, but git from a non-Azure source (e.g., my local desktop), so I know the access token framework is working; it's got to be something with the way Azure is trying to configure the scenario.
I've tried creating new App Services on the same subscription as my VSTS account and AAD directory, and then linking those. The result is the same.
I've also tried setting up the deployment in the old Azure portal. That resulted in the creation of a new OAuth authorization for the account. But, ultimately, I got the same failures.
At this point, it seems like Azure thinks that it's creating a new personal access token in my VSTS account, but the new token doesn't seem to be sticking.
Anyone have any suggestions? Either a permissions issue that I'm missing on the VSTS side, or maybe something in the AAD user settings or security? Something in Azure?
Hi,
Thanks for posting here.
VSTS will need a secure connection to the Azure subscription, this connection is service principal based, so you need to have an AAD backing your Azure subscription and you need to have permissions to add new applications to the AAD by having the administrator or co-admin permissions. I would suggest you check for the administrator and co-admin permissions and let us know the feedback.
Please go through the below document for more information:
http://www.colinsalmcorner.com/post/continuous-deployment-of-service-fabric-apps-using-vsts-or-tfs
Regards,
Disclaimer:
This response contains a reference to a third party World Wide Web site. Microsoft is providing this information as a convenience to you. Microsoft does not control these sites and has not tested any software or information found on these sites; therefore, Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. There are inherent dangers in the use of any software found on the Internet, and Microsoft cautions you to make sure that you completely understand the risk before retrieving any software from the Internet.
这篇关于Azure App Service& lt; - & gt; VSTS部署失败（状态代码：500）at& quot;获取更改& quot;步的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
