From f5ac538879aa5d82d9517bedf051c9609eb28349 Mon Sep 17 00:00:00 2001 From: DXPetti Date: Tue, 19 Dec 2023 11:28:39 +1100 Subject: [PATCH 1/3] Update Frequently-Asked-Questions.md Added example of invalid characters creating operation failures based upon closed issue #822 --- docs/wiki/Frequently-Asked-Questions.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/wiki/Frequently-Asked-Questions.md b/docs/wiki/Frequently-Asked-Questions.md index b4c39c99..507d66e9 100644 --- a/docs/wiki/Frequently-Asked-Questions.md +++ b/docs/wiki/Frequently-Asked-Questions.md @@ -32,6 +32,10 @@ To confirm if this applies to you, check the pipeline logs for any of the follow Remove the invalid resource or character and retry the operation. +A common example of a invalid characters preventing successful operations in AzOps is with [Visual Studio Enterprise](https://azure.microsoft.com/en-us/pricing/offers/ms-azr-0063p/) based subscriptions. The default resource name of said subscriptions contains the "`–`" [EN DASH](https://www.cogsci.ed.ac.uk/~richard/utf-8.cgi?input=2013&mode=hex) character. For example: + +`visual studio enterprise subscription – mpn` + ## Push fail with deployment already exists in location error If you have changed `"Core.DefaultDeploymentRegion":` from the default `northeurope` post initial setup, subsequent Push/Deployments might fail with an error as below: From c6281a616770b00a383e1c2b2b27e17bebaf1684 Mon Sep 17 00:00:00 2001 From: Johan Dahlbom Date: Tue, 19 Dec 2023 10:43:51 +0100 Subject: [PATCH 2/3] Update Frequently-Asked-Questions.md --- docs/wiki/Frequently-Asked-Questions.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/docs/wiki/Frequently-Asked-Questions.md b/docs/wiki/Frequently-Asked-Questions.md index 507d66e9..6483fb88 100644 --- a/docs/wiki/Frequently-Asked-Questions.md +++ b/docs/wiki/Frequently-Asked-Questions.md @@ -32,9 +32,8 @@ To confirm if this applies to you, check the pipeline logs for any of the follow Remove the invalid resource or character and retry the operation. -A common example of a invalid characters preventing successful operations in AzOps is with [Visual Studio Enterprise](https://azure.microsoft.com/en-us/pricing/offers/ms-azr-0063p/) based subscriptions. The default resource name of said subscriptions contains the "`–`" [EN DASH](https://www.cogsci.ed.ac.uk/~richard/utf-8.cgi?input=2013&mode=hex) character. For example: +A common example of invalid characters preventing successful operations in AzOps is with [Visual Studio Enterprise](https://azure.microsoft.com/en-us/pricing/offers/ms-azr-0063p/) based subscriptions. The default resource name of said subscriptions contains the "`–`" [EN DASH](https://www.cogsci.ed.ac.uk/~richard/utf-8.cgi?input=2013&mode=hex) character. Example: `visual studio enterprise subscription – mpn`. -`visual studio enterprise subscription – mpn` ## Push fail with deployment already exists in location error From 0a68851d7b6e751d1a56eec3fe16e6cb7f38a4ea Mon Sep 17 00:00:00 2001 From: Johan Dahlbom Date: Tue, 19 Dec 2023 10:46:08 +0100 Subject: [PATCH 3/3] Update Frequently-Asked-Questions.md --- docs/wiki/Frequently-Asked-Questions.md | 1 - 1 file changed, 1 deletion(-) diff --git a/docs/wiki/Frequently-Asked-Questions.md b/docs/wiki/Frequently-Asked-Questions.md index 6483fb88..bb4efe7e 100644 --- a/docs/wiki/Frequently-Asked-Questions.md +++ b/docs/wiki/Frequently-Asked-Questions.md @@ -34,7 +34,6 @@ Remove the invalid resource or character and retry the operation. A common example of invalid characters preventing successful operations in AzOps is with [Visual Studio Enterprise](https://azure.microsoft.com/en-us/pricing/offers/ms-azr-0063p/) based subscriptions. The default resource name of said subscriptions contains the "`–`" [EN DASH](https://www.cogsci.ed.ac.uk/~richard/utf-8.cgi?input=2013&mode=hex) character. Example: `visual studio enterprise subscription – mpn`. - ## Push fail with deployment already exists in location error If you have changed `"Core.DefaultDeploymentRegion":` from the default `northeurope` post initial setup, subsequent Push/Deployments might fail with an error as below: