Skip to content

Commit 46be134

Browse files
committed
revert the change
1 parent 6a1503f commit 46be134

File tree

2 files changed

+132
-0
lines changed

2 files changed

+132
-0
lines changed
Lines changed: 90 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,90 @@
1+
---
2+
title: Deployment FAQs for Web Apps
3+
description: Get answers to frequently asked questions about deployment for the Web Apps feature of Azure App Service.
4+
author: genlin
5+
ms.author: genli
6+
ms.service: azure-cloud-services-classic
7+
ms.date: 03/09/2022
8+
ms.reviewer: toan, shrahman
9+
---
10+
# Deployment FAQs for Web Apps in Azure
11+
12+
This article has answers to frequently asked questions (FAQs) about deployment issues for the [Web Apps feature of Azure App Service](https://azure.microsoft.com/services/app-service/web/).
13+
14+
[!INCLUDE [support-disclaimer](../../includes/support-disclaimer.md)]
15+
16+
## I'm just getting started with App Service web apps. How do I publish my code?
17+
18+
Here are some options for publishing your web app code:
19+
20+
- Deploy by using Visual Studio. If you have the Visual Studio solution, right-click the web application project, and then select **Publish**.
21+
- Deploy by using an FTP client. In the Azure portal, download the publish profile for the web app that you want to deploy your code to. Then, upload the files to \\site\\wwwroot by using the same publish profile FTP credentials.
22+
23+
For more information, see [Deploy your app to App Service](/azure/app-service/deploy-local-git).
24+
25+
## I see an error message when I try to deploy from Visual Studio. How do I resolve this error?
26+
27+
If you see the following message, you might be using an older version of the SDK:
28+
29+
> Error during deployment for resource 'YourResourceName' in resource group 'YourResourceGroup': MissingRegistrationForLocation: The subscription is not registered for the resource type 'components' in the location 'Central US'. Re-register for this provider in order to have access to this location.
30+
31+
To resolve this error, upgrade to the [latest SDK](https://azure.microsoft.com/downloads/). If you see this message and you have the latest SDK, submit a support request.
32+
33+
## How do I deploy an ASP.NET application from Visual Studio to App Service?
34+
35+
The tutorial [Create your first ASP.NET web app in Azure in five minutes](/azure/app-service/quickstart-dotnetcore) shows you how to deploy an ASP.NET web application to a web app in App Service by using Visual Studio.
36+
37+
## What are the different types of deployment credentials?
38+
39+
App Service supports two types of credentials for local Git deployment and FTP/S deployment. For more information about how to configure deployment credentials, see [Configure deployment credentials for App Service](/azure/app-service/deploy-configure-credentials).
40+
41+
## What is the file or directory structure of my App Service web app?
42+
43+
For information about the file structure of your App Service app, see [File structure in Azure](https://github.com/projectkudu/kudu/wiki/File-structure-on-azure).
44+
45+
## How do I resolve "FTP Error 550 - There isn't enough space on the disk" when I try to FTP my files?
46+
47+
If you see this message, it's likely that you're running into a disk quota in the service plan for your web app. You might need to scale up to a higher service tier based on your disk space needs. For more information about pricing plans and resource limits, see [App Service pricing](https://azure.microsoft.com/pricing/details/app-service/).
48+
49+
## How do I set up continuous deployment for my App Service web app?
50+
51+
You can set up continuous deployment from several resources, including Azure DevOps, OneDrive, GitHub, Bitbucket, Dropbox, and other Git repositories. These options are available in the portal. [Continuous deployment to App Service](/azure/app-service/deploy-continuous-deployment) is a helpful tutorial that explains how to set up continuous deployment.
52+
53+
## How do I troubleshoot issues with continuous deployment from GitHub and Bitbucket?
54+
55+
For help investigating issues with continuous deployment from GitHub or Bitbucket, see [Investigating continuous deployment](https://github.com/projectkudu/kudu/wiki/Investigating-continuous-deployment).
56+
57+
## I can't FTP to my site and publish my code. How do I resolve this issue?
58+
59+
To resolve FTP issues, follow these steps:
60+
61+
1. Verify that you're entering the correct host name and credentials. For detailed information about different types of credentials and how to use them, see [Deployment credentials](https://github.com/projectkudu/kudu/wiki/Deployment-credentials).
62+
2. Verify that the FTP ports aren't blocked by a firewall. The ports should have these settings:
63+
- FTP control connection port: 21
64+
- FTP data connection port: 989, 10001-10300
65+
66+
## How do I publish my code to App Service?
67+
68+
The Azure Quickstart is designed to help you deploy your app by using the deployment stack and method of your choice. To use the Quickstart, in the Azure portal, go to your app service, under **Deployment**, select **Quickstart**.
69+
70+
## Why does my app sometimes restart after deployment to App Service?
71+
72+
To learn about the circumstances under which an application deployment might result in a restart, see [Deployment vs. runtime issues](https://github.com/projectkudu/kudu/wiki/Deployment-vs-runtime-issues#deployments-and-web-app-restarts"). As the article describes, App Service deploys files to the wwwroot folder. It never directly restarts your app.
73+
74+
## How do I integrate Azure DevOps code with App Service?
75+
76+
You have two options for using continuous deployment with Azure DevOps:
77+
78+
- Use a Git project. Connect via App Service by using the Deployment Center.
79+
- Use a Team Foundation Version Control (TFVC) project. Deploy by using the build agent for App Service.
80+
81+
Continuous code deployment for both these options depends on existing developer workflows and check-in procedures. For more information, see these articles:
82+
83+
- [Implement continuous deployment of your app to an Azure website](/azure/devops/pipelines)
84+
- [Set up an Azure DevOps organization so it can deploy to a web app](https://github.com/projectkudu/kudu/wiki/Setting-up-a-VSTS-account-so-it-can-deploy-to-a-Web-App)
85+
86+
## How do I use FTP or FTPS to deploy my app to App Service?
87+
88+
For information about using FTP or FTPS to deploy your web app to App Service, see [Deploy your app to App Service by using FTP/S](/azure/app-service/deploy-ftp).
89+
90+
[!INCLUDE [Azure Help Support](../../includes/azure-help-support.md)]
Lines changed: 42 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,42 @@
1+
---
2+
title: Troubleshoot Microsoft Azure Cloud Service (classic) VIP swap failures 123
3+
description: Troubleshoot cloud service VIP swap failures (VipS123wapNotAllowedAsRollingUpgradeIsInProgress exceptions) in Azure Cloud Service (classic).
4+
ms.service: azure-cloud-services-classic
5+
ms.date: 09/26/2024
6+
ms.reviewer: chiragpa, v-leedennis
7+
ms.custom: sap:Deployment
8+
---
9+
10+
11+
## AADSTS50070
12+
The request failed with the following exception: AADSTS50070: Signout failed. The request specified session indexes '_cbxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx00' which did not match the existing session(s).
13+
14+
Issue :-
15+
when we customers have two SAML sessions active , SAMLResponce1 (with SessionIndex="_cb4xxxxxx-xxxx-xxxx-xxxx-bxxxxxxxxxxx) and SAML Response 2 ( with SessionIndex="_d69xxxx-xxxx-xxxx-xxxx-bxxxxxxxxxx) and when the user logout and logout request contains the ( SessionIndex="_cb4xxxx-xxxx-xxxx-xxxx-bxxxxxxxxxxx ) , log out fails with the error AADSTS50070: Signout failed. The request specified session indexes '_cbxxxxx-xxxx-xxxx-xxxx-bxxxxxxxxxxx ' which did not match the existing session(s).
16+
17+
Solution: -
18+
19+
This is not a problem with ESTS. There seems to be a browser and an app problem.
20+
21+
Example SessionIndex in SAML response
22+
====================================
23+
24+
Name="http://schemas.xmlsoap.org/ws/2005/05/identity/claims/storeId "><AttributeValue>1</AttributeValue></Attribute><Attribute Name="http://schemas.xmlsoap.org/ws/2005/05/identity/claims/StoreName"><AttributeValue>Masked</AttributeValue></Attribute></AttributeStatement><AuthnStatement AuthnInstant="2022-04-06T07:30:07.182Z" SessionIndex="_cbxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx "><AuthnContext><AuthnContextClassRef>urn:oasis:names:tc:SAML:2.0:ac:classes:Password</AuthnContextClassRef></AuthnContext></AuthnStatement></Assertion></samlp:Response>
25+
26+
User might have got another token and this time the SAML response is below
27+
28+
Name="http://schemas.xmlsoap.org/ws/2005/05/identity/claims/storeId "><AttributeValue>1</AttributeValue></Attribute><Attribute Name="http://schemas.xmlsoap.org/ws/2005/05/identity/claims/StoreName"><AttributeValue>Masked</AttributeValue></Attribute></AttributeStatement><AuthnStatement AuthnInstant="2022-04-06T07:30:07.182Z" SessionIndex="_d6xxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx "><AuthnContext><AuthnContextClassRef>urn:oasis:names:tc:SAML:2.0:ac:classes:Password</AuthnContextClassRef></AuthnContext></AuthnStatement></Assertion></samlp:Response>
29+
30+
The SessionIndex value must be used again when the user logs out.
31+
32+
Example Logout
33+
===========
34+
35+
SAML Logout Request:
36+
37+
<saml2p:LogoutRequest Destination="https://login.microsoftonline.com/TenantGuid/saml2 " ID="_6e25867b-4629-40aa-8a2a-0e345050faf4" IssueInstant="2022-04-06T07:30:16.268Z" NotOnOrAfter="2022-04-06T07:35:16.268Z" Version="2.0" xmlns:saml2p="urn:oasis:names:tc:SAML:2.0:protocol"><saml2:Issuer Format="urn:oasis:names:tc:SAML:2.0:nameid-format:entity" xmlns:saml2="urn:oasis:names:tc:SAML:2.0:assertion">Masked </saml2:Issuer><saml2:NameID Format="urn:oasis:names:tc:SAML:2.0:nameid-format:persistent" xmlns:saml2="urn:oasis:names:tc:SAML:2.0:assertion">[email protected]</saml2:NameID>saml2p:SessionIndex _cbxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx </saml2p:SessionIndex></saml2p:LogoutRequest>
38+
39+
Log out fails with error AADSTS50070
40+
41+
The SAML session index is continuously updated when an application requests new tokens. There are no two session indexes that server maintains , but just one. SP must send the latest session index when signing out users. If SP sends previous or old Session Index then we gave the above stated error. Issue would be with browser just didn’t send the correct or latest cookies or it sent old cookies , customer or app developer needs to figure out .
42+

0 commit comments

Comments
 (0)