Do you have a sample implementation using Jenkins ?

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: a0e54ed0-e139-1569-adc8-1833de468eb9
• Version Independent ID: 0b03d258-e1ee-e59b-997f-e9096c6f53e2
• Content: Deploy your app to Azure and Azure Stack
• Content Source: azure-stack/user/azure-stack-solution-pipeline.md
• Service: azure-stack
• GitHub Login: @mattbriggs
• Microsoft Alias: mabrigg

Update Test-AzureStack document section "Run validation tool to test system readiness before installing update or hotfix"

With new parameter option added in 1902 update- "To improve the Azure Stack operator experience when running Test-AzureStack, operators can now simply use Test-AzureStack -Group UpdateReadiness instead of passing ten additional parameters after an include statement. "
From- https://docs.microsoft.com/en-us/azure/azure-stack/azure-stack-update-1902#improvements

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: eacef4e6-6608-bfab-ceea-d081b9c48e3a
• Version Independent ID: e260c6a1-7cec-2c32-76b6-a80ce0ac00fe
• Content: Use the Azure Stack validation tool
• Content Source: articles/azure-stack/azure-stack-diagnostic-test.md
• Service: azure-stack
• GitHub Login: @jeffgilb
• Microsoft Alias: jeffgilb

Hello fellow documentarians!

First off, I'd like to thank each of you for participating in the Write the Docs writing day. We appreciate you spending time with us while we work towards building more inclusive documentation.

The Goal

At Microsoft, our mission is to empower every person and every organization on the planet to achieve more. To realize this mission, we need to ensure that our documentation speaks to a global audience and is inclusive of all.

We are seeking your help to assist us in ensuring our documentation is more inclusive. Review the resources below, as they will help you on your way.

We are asking for your help in the following ways:

• Provide an update from our curated list of suggestions
• Update a topic you are familiar with, which has an issue
• File an issue on content in which you’ve found an issue

How to contribute from the curated list of suggestions

1. Review the list of GitHub Issues to find suggested updates curated by our team
2. Provide a comment on an issue that you are picking up, to avoid duplicate effort
3. Fix the issue(s) outlined in the GitHub Issue
4. Create a Pull Request to submit the fix
   1. Start the PR title with [WTD]

How to contribute to a topic you are familiar with

1. Browse to the article on docs.microsoft.com
2. Select the edit button in the header to be redirected to the article on GitHub
3. Select the pencil icon, and edit the relevant lines of the article
4. SelectPropose file change, in the GitHub UI to create a pull request
   1. Start the PR title with [WTD]

File an issue on content in which you’ve found an issue

1. Browse to an article on docs.microsoft.com
2. Under the Feedback header at the bottom of the page, select the “This page” button under the Send feedback about text.
   1. Start the Issue Title with [WTD]
3. Leave a descriptive comment to help us narrow down how to resolve the issue
   1. Include a link to one of the Inclusive Language resources below (or others you know of) -- help us grow and learn, as well!

Resources

• Gender Inclusive Language Guidelines – UN
• Inclusive Language in Four Easy Steps - Harvard

Repositories in Scope

• Azure Docs
• PowerBI Docs
• System Center Configuration Manager (SCCM) Docs

Assuming you follow this page (important goto-place) for configuring FW you won't be able to connect a Azure VPN to the Azure Stack VPN.
It is listed in the FAQ for VPN though, but I strongly belive this page should include such important information when we use this page for planning.

Ref:
• https://docs.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-vpn-faq
o IKEv2 VPN. IKEv2 VPN is a standards-based IPsec VPN solution that uses UDP port 500 and 4500 and IP protocol no. 50. Firewalls do not always open these ports, so there is a possibility of IKEv2 VPN not being able to traverse proxies and firewalls.

Dokumentinformasjon

⚠ Ikke rediger denne delen. Den kreves for koblingen docs.microsoft.com ➟ GitHub-problem.

• ID: 4bf65509-158a-6ae7-60f0-586170fab6af
• Version Independent ID: 18f15ad2-ef9b-f883-c49b-09289a2e6fb8
• Content: Azure Stack datacenter integration - Publish endpoints
• Content Source: articles/azure-stack/azure-stack-integrate-endpoints.md
• Service: azure-stack
• GitHub Login: @jeffgilb
• Microsoft Alias: jeffgilb

According to the release notes of App Service 1.5, in case it's deployed in HA, the DB must be added to the AG.
https://docs.microsoft.com/en-us/azure/azure-stack/azure-stack-app-service-release-notes-update-five

That would be good to have it here otherwise it's not really an HA architecture and it will fail at some point...
Thank you.

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 191cc116-9bd7-171c-cdfc-f48c41aef252
• Version Independent ID: a9a47181-f4c6-51d0-caea-e06d67996e60
• Content: Deploy Azure Stack App Service in a highly available configuration
• Content Source: articles/azure-stack/app-service-deploy-ha.md
• Service: azure-stack
• GitHub Login: @jeffgilb
• Microsoft Alias: jeffgilb

I don't follow where to click.

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 46d0432d-8bdf-ae6a-000c-4da12913b759
• Version Independent ID: e14583a3-c977-106e-0211-a516734e3965
• Content: Deploy templates using the portal in Azure Stack
• Content Source: articles/azure-stack/user/azure-stack-deploy-template-portal.md
• Service: azure-stack
• GitHub Login: @sethmanheim
• Microsoft Alias: sethm

The App Services update 5 offline install appears to have a missing depency for offline installs. The install requires the newtonsoft.json powershell library in order to parse the initial ARM endpoints. This package is not included in the offline install package and is not mentioned in the "before you get started" documentation.

Without the newtonsoft.json package installed you get the following errors in the app server install log:

System.IO.FileNotFoundException: Could not load file or assembly 'Newtonsoft.Json', Version=8.0.0.0.......

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 603ac047-9a9e-1841-c3a4-bc037edf7f64
• Version Independent ID: 19bbf07b-c7e4-263d-7678-eaf8ad9e3fe3
• Content: Update Azure App Service Offline
• Content Source: azure-stack/operator/azure-stack-app-service-update-offline.md
• Service: azure-stack
• GitHub Login: @mattbriggs
• Microsoft Alias: anwestg

As an CSP Azure stack provider, I have folllowed above steps but unable to carry out task #3:

Your CSP should create a resource in your subscription to verify that they can manage your resources.

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 11a1cde5-1b89-2868-4768-3e2c55cee5a1
• Version Independent ID: 670abaf8-6088-b5a8-e13b-36930c40d74e
• Content: Enable a Cloud Service Provider to manage your Azure Stack subscription
• Content Source: azure-stack/user/azure-stack-csp-enable-billing-usage-tracking.md
• Service: azure-stack
• GitHub Login: @sethmanheim
• Microsoft Alias: sethm

Character "_" creates a problem with the 1903 update while deploying the "Quickstart template for Highly Available File Server and SQL Server" thru the Admin Portal. Template deployment fails to start. To deploy the template successfully, use Powershell instead of admin portal.

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 2c085e86-242e-ac36-a611-3d379d3dcfb0
• Version Independent ID: 4d455fad-dc6a-ed4f-75c0-f8a6118aa07a
• Content: Before you deploy App Service on Azure Stack
• Content Source: azure-stack/operator/azure-stack-app-service-before-you-get-started.md
• Service: azure-stack
• GitHub Login: @jeffgilb
• Microsoft Alias: anwestg

Step 2 in the Prepare for the CLI does not seem to be accurate. After creating a VM on Stack (1.1903.2.39) there is no certificate with the label "AzureStackSelfSignedRootCert".

Steps to reproduce:
Create a Windows Server 2016 Datacenter server on Azure Stack
Sign into the machine and open elevated PowerShell windows
Run the provided script to find the StackSelfSignedRootCert

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 583c4bab-c16a-a723-04ac-b3265d9e8269
• Version Independent ID: e6ecb0ee-2303-a7ed-9fca-767e3d3bfe86
• Content: Connect to Azure Stack with CLI
• Content Source: azure-stack/user/azure-stack-version-profiles-azurecli2.md
• Service: azure-stack
• GitHub Login: @mattbriggs
• Microsoft Alias: mabrigg

The script on this page for collecting AzureStack logs after a failure of Test-AzureStack does not work as written. I suggest you add the commands that are needed to make it work.

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: eacef4e6-6608-bfab-ceea-d081b9c48e3a
• Version Independent ID: e260c6a1-7cec-2c32-76b6-a80ce0ac00fe
• Content: Use the Azure Stack validation tool
• Content Source: articles/azure-stack/azure-stack-diagnostic-test.md
• Service: azure-stack
• GitHub Login: @jeffgilb
• Microsoft Alias: jeffgilb

The steps under "Create a service principal" appear to be using Azure Portal blade now called "App registrations (Legacy)".
Per the public Azure portal- "App registrations (Legacy) will be replaced and no longer available starting May 2019. Go to the new and improved App registrations (now Generally Available)."

Please update this document to use the new-style App Registrations before the old one is unavailable.

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: b60c4726-881a-a32c-6a85-25ca65a31c00
• Version Independent ID: a40334b6-dca7-52f7-62c3-3b8ecba6d606
• Content: Deploy Kubernetes to Azure Stack using Azure Active Directory (Azure AD)
• Content Source: azure-stack/user/azure-stack-solution-template-kubernetes-azuread.md
• Service: azure-stack
• GitHub Login: @mattbriggs
• Microsoft Alias: mabrigg

Using the latest AzS.Deployment.Worksheet PowerShell module, the field description says the following for the Time Server: field

Enter a single IPv4 address or a single FQDN to be used as a reliable time source.
NOTE: If a FQDN is specified, all of the network devices must support the use of a FQDN, otherwise validation will fail.

I attemped to use an FQDN for all 8 Vendor switches available in the list and all of them failed with the following error

(ntp.domain.local) is not valid as a Time Server. If entering a FQDN, all switches must support FQDN for switch NTP. Contact OEM for support information.

I was working with my OEM rep and they were unsure how to proceed. Since all vendor switches throw an error this option should be removed until FQDN is actually supported.

UPDATE
I am using version v1.1811.1214.1 of the PowerShell module

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 147eee4f-8b0f-927a-14ff-5642accb3610
• Version Independent ID: 95213ed3-d96f-8ad9-e442-7c7f29164ebb
• Content: Network integration considerations for Azure Stack integrated systems
• Content Source: articles/azure-stack/azure-stack-network.md
• Service: azure-stack
• GitHub Login: @jeffgilb
• Microsoft Alias: jeffgilb

Hi,

My understanding is that OUTBOUND DNS is required for initial deployment only, and not for day-to-day operation. It states as much in the DNS integration section earlier in this document. Could this be clarified as some customers want to keep their public ports as locked down as possible?

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 4bf65509-158a-6ae7-60f0-586170fab6af
• Version Independent ID: 18f15ad2-ef9b-f883-c49b-09289a2e6fb8
• Content: Azure Stack datacenter integration - Publish endpoints
• Content Source: articles/azure-stack/azure-stack-integrate-endpoints.md
• Service: azure-stack
• GitHub Login: @jeffgilb
• Microsoft Alias: jeffgilb

This program is no longer hosted on that link (MS Connect). For more info go here:
https://docs.microsoft.com/en-us/office365/enterprise/powershell/connect-to-office-365-powershell

Therefore do these from that article:

Step 1: Install required software
These steps are required once on your computer, not every time you connect. However, you'll likely need to install newer versions of the software periodically.

Install the 64-bit version of the Microsoft Online Services Sign-in Assistant: Microsoft Online Services Sign-in Assistant for IT Professionals RTW.

Install the Microsoft Azure Active Directory Module for Windows PowerShell with these steps:

Open an elevated Windows PowerShell command prompt (run Windows PowerShell as an administrator).
Run the Install-Module MSOnline command.
If prompted to install the NuGet provider, type Y and press ENTER.
If prompted to install the module from PSGallery, type Y and press ENTER.

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 2b2adbad-6f3d-02af-c936-694f98597cb9
• Version Independent ID: fdc8c0cb-eb86-0b3a-595c-162e18f67d54
• Content: Add a new Azure Stack tenant account in Azure Active Directory
• Content Source: azure-stack/operator/azure-stack-add-new-user-aad.md
• Service: azure-stack
• GitHub Login: @PatrickA
• Microsoft Alias: patricka

hi, I ´ve following the steps to create certificates in my Azure Stack (integrated systems no SDK!!!) however the Get-AzureStackRootCert.ps1 command can´t find the Endpoint I fix it adding the IP and hostname to my hosts file.
Then I go forward to run the Create-AppServiceCerts.ps1 script but It fails with errors as follows:

New-SelfSignedCertificate : Cannot bind parameter 'Signer' to the target. Exception setting "Signer": "Value cannot be null.
Parameter name: Signer"
At C:\appservice\Create-AppServiceCerts.ps1:38 char:140

• ... ocation Cert:\LocalMachine\My -DnsName $DnsName -Signer $root -Provid ...

•                                                         ~~~~~
  

  • CategoryInfo : WriteError: (:) [New-SelfSignedCertificate], ParameterBindingException
  • FullyQualifiedErrorId : ParameterBindingFailed,Microsoft.CertificateServices.Commands.NewSelfSignedCertificateCommand

So there is another way to create certificates to enable App Services on my Azure Stack? or there is something that I missed?

regards

S_

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 4b745d67-f3a8-3a4a-5b89-c0e5851ef5e0
• Version Independent ID: 4d455fad-dc6a-ed4f-75c0-f8a6118aa07a
• Content: Before you deploy App Service on Azure Stack
• Content Source: articles/azure-stack/azure-stack-app-service-before-you-get-started.md
• Service: azure-stack
• GitHub Login: @apwestgarth
• Microsoft Alias: anwestg

Hello
Why are there two build numbers for the SQL RP? Both supporting the same Azure Stack build. Reference pages are also misaligned. PowerShell compatibility was fixed with 1.1.30.0 however, 1.1.33.0 is a later build. Which version do we use? Both installs fail with the latest ASDK environment.

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: dabc86bd-3770-5832-7fa5-d28856998ae6
• Version Independent ID: cbdb8c6f-ad4d-9e3d-a490-f1348b5ccdfa
• Content: Using SQL databases on Azure Stack
• Content Source: azure-stack/operator/azure-stack-sql-resource-provider-deploy.md
• Service: azure-stack
• GitHub Login: @jeffgilb
• Microsoft Alias: jeffgilb

testing from warchtower, will delete it

The whole topic is not necessary anymore, it defaults now (1901) to 679 days

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: be299a6e-e10b-ae65-a59d-e5730e33a54d
• Version Independent ID: 9dc0a609-b728-7198-a2c0-8408c6ec91c6
• Content: Post deployment configurations for the Azure Stack Development Kit (ASDK)
• Content Source: articles/azure-stack/asdk/asdk-post-deploy.md
• Service: azure-stack
• GitHub Login: @jeffgilb
• Microsoft Alias: jeffgilb

Here is a powershell script that I ran from Windows 10 which results in the Invalid URI error. This is using the unmodified example. I have also tried modifying the example extensively with no success. What changes need to be made in order for the packager to succeed?

wget http://www.aka.ms/azurestackmarketplaceitem -OutFile example.zip
Expand-Archive .\example.zip
cd '.\example\Azure Stack Marketplace Item Generator and Sample'
.\AzureGalleryPackageGenerator\AzureGalleryPackager.exe package -m .\SimpleVMTemplate\manifest.json -o .

Result:

Invalid URI: The format of the URI could not be determined.

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 83d0ba3d-9766-30da-70f0-5f4c3ec9a47e
• Version Independent ID: 6a9509a1-f16c-f527-5df1-9dae2d8eeaed
• Content: Create and publish a Marketplace item in Azure Stack
• Content Source: articles/azure-stack/azure-stack-create-and-publish-marketplace-item.md
• Service: azure-stack
• GitHub Login: @sethmanheim
• Microsoft Alias: sethm

Created an installation user account with "User" right of their tenant directory (without Global Admin). Then executed the validation script on the following url.

https://docs.microsoft.com/en-us/azure/azure-stack/azure-stack-validate-identity

The script output was OK.
I think that this script doesn't check "Global Admin" right.

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 180ae274-132e-dd31-19cf-71eac378dc21
• Version Independent ID: de499123-09f5-e6f5-176c-f63994e8f758
• Content: Validate Azure Identity for Azure Stack
• Content Source: azure-stack/operator/azure-stack-validate-identity.md
• Service: azure-stack
• GitHub Login: @sethmanheim
• Microsoft Alias: sethm

A note should be added explaining there is a different in content between the connected and disconnected marketplaces. For example, a connected Azure Stack has over 20 variants of F5 BIG-IP load balancers, but the marketplace syndication tool shows only 3 of the 20 are available. Several other items from the marketplace are missing as well.

It would be useful to explain why there is a difference and if its a matter of timing or if some items are not authorized for disconnected Azure Stack versus connected.

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: da2c689d-3537-c125-3f00-d769c9b5aa0c
• Version Independent ID: 81e5de2b-da67-e875-405d-65628be05adc
• Content: Download marketplace items from Azure
• Content Source: articles/azure-stack/azure-stack-download-azure-marketplace-item.md
• Service: azure-stack
• GitHub Login: @sethmanheim
• Microsoft Alias: sethm

The "connect to Azure and register" paragraph needs to be split out into the specific commands that are needed to accomplish this step just like they are in the two connected examples above. The example scripts in this section contain variables that are not defined in the script themselves. It assumes that previous commands were run in the same session. Please add clarification and specific steps to this section to make the process clearer to the person performing the steps.

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 3a3a708a-4424-0d9c-68f7-20e15e214a5a
• Version Independent ID: 5a7921c1-ac2e-6de8-0e8d-de9f04e457a6
• Content: Azure registration for Azure Stack integrated systems
• Content Source: articles/azure-stack/azure-stack-registration.md
• Service: azure-stack
• GitHub Login: @jeffgilb
• Microsoft Alias: jeffgilb

If you follow this step by step, in will not work. You Should create the VNets, Subnets and Virtual Network GWs first on each side. If you do that THEN you ca do this step "type the public IP address for your Azure Stack Virtual Network Gateway that is listed previously in the network configuration table." - which is listed in the Azure section, but before anything had been done in Azure Stack. Therefore, you will not have the IP Address for the Azure Stack VNet GW, because it has not been created yet.

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: fec5666f-c9b6-2ae6-3a46-3b390d252d19
• Version Independent ID: cbdfbfc9-a835-2015-ce60-a6e0578c4d4a
• Content: Connect Azure Stack to Azure using VPN
• Content Source: articles/azure-stack/azure-stack-connect-vpn.md
• Service: azure-stack
• GitHub Login: @sethmanheim
• Microsoft Alias: sethm

Hello, the schema https://docs.microsoft.com/en-us/azure/azure-stack/media/azure-stack-integrate-dns/integrate-dns-01.png is incorrect :

• Name servers are azs-ns01/ns02 and not azs-Dns01/Dns02 (the D should be removed)
• forwarded zone should be the same as in the text (east.cloud.fabrikam.com and not sea.azurestack.external)
• another zone should be included in the ns01/ns02 servers : east.cloudapp.cloud.fabrikam.com)

Please update it to match the rest of the doc.

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 4cf7c779-041d-a232-b441-b769be1aaa67
• Version Independent ID: 2b4f5bc1-66f6-4c7f-c06e-bc32f2acd383
• Content: Azure Stack datacenter integration - DNS
• Content Source: articles/azure-stack/azure-stack-integrate-dns.md
• Service: azure-stack
• GitHub Login: @jeffgilb
• Microsoft Alias: jeffgilb

Core ratio column in the table above displays the virtual to physical core ratio. It displays ratio as 4.3 for 1st row, 4:1 for 2nd row and 3:1 for 3rd row.

When I calculate the ratio between virtual to physical ratio, it comes about 27:28 for 1st row and 18:7 for 2nd and 3rd row.

My calculation is based on following table.

Can you please take a look and correct it accordingly?

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: a892fa3c-5403-6cbe-d9dc-23839807ec5b
• Version Independent ID: e2eb938a-1a20-d94b-63d6-c8b66f1a8dad
• Content: Capacity planning for Azure Stack
• Content Source: articles/azure-stack/capacity-planning.md
• Service: azure-stack
• GitHub Login: @jeffgilb
• Microsoft Alias: jeffgilb

Because Azure RM powershell 2.4.0 version doesn't allow to use hybrid profile, Azure RM powershell 2.3.0 should be used with custom script deployment. Additionaly, since Azure Stack powershell 1.7.0 is incompatible with Azure RM 2.3.0, Azure Stack powershell 1.5.0 or 1.6.0 must be used in conjunction with Azure RM 2.3.0.

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 2f7e3b4a-30fb-4068-32b1-943cd483f531
• Version Independent ID: fc78fd4f-2626-e0b9-8ac0-7ea1938ff419
• Content: Using MySQL databases on Azure Stack
• Content Source: azure-stack/operator/azure-stack-mysql-resource-provider-deploy.md
• Service: azure-stack
• GitHub Login: @jeffgilb
• Microsoft Alias: jeffgilb

Hello,

The following way to add a vm image through portal is incorrect.

https://docs.microsoft.com/en-us/azure-stack/operator/azure-stack-add-vm-image#add-a-vm-image-through-the-portal

I think that a image in Azure Stack is two types. A is a image which is in a specific subscription. B is a image which is in the platform of Azure Stack. Azure Stack Operator must create a image as B to use a image as Azure Stack Marketplace, but this article introduce a way about A.

Best regards.

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: d6a61eee-2c60-1a86-3e06-fa7689705d18
• Version Independent ID: 28759edc-2b94-e42e-3353-6ebe13b2a90f
• Content: Add a VM image to Azure Stack
• Content Source: azure-stack/operator/azure-stack-add-vm-image.md
• Service: azure-stack
• GitHub Login: @mattbriggs
• Microsoft Alias: mabrigg

[Enter feedback here]
in

foreach($s in (Get-AzureRmSubscription)) {
Select-AzureRmSubscription -SubscriptionId $s.SubscriptionId | Out-Null
Write-Progress $($s.SubscriptionId + " : " + $s.SubscriptionName)
Get-AzureRmResourceProvider -ListAvailable | Register-AzureRmResourceProvider -Force
}

-Force is not a Parameter
Register-AzureRmResourceProvider : A parameter cannot be found that matches parameter name 'Force'.
At line:4 char:79

• ... urceProvider -ListAvailable | Register-AzureRmResourceProvider -Force

•                                                                ~~~~~~
  

  • CategoryInfo : InvalidArgument: (:) [Register-AzureRmResourceProvider], ParameterBindingException
  • FullyQualifiedErrorId : NamedParameterNotFound,Microsoft.Azure.Commands.ResourceManager.Cmdlets.Implementation.RegisterAzureProviderCmdlet

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: b1427fb3-7704-d83a-45df-a68e76fcb2b9
• Version Independent ID: d995f898-b0e3-1cdc-4d19-db5145f46896
• Content: Connect to Azure Stack with PowerShell as a user
• Content Source: azure-stack/user/azure-stack-powershell-configure-user.md
• Service: azure-stack
• GitHub Login: @mattbriggs
• Microsoft Alias: mabrigg

Because Azure RM powershell 2.4.0 version doesn't allow to use hybrid profile, Azure RM powershell 2.3.0 should be used with custom script deployment. Additionaly, since Azure Stack powershell 1.7.0 is incompatible with Azure RM 2.3.0, Azure Stack powershell 1.5.0 or 1.6.0 must be used in conjunction with Azure RM 2.3.0.

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: dabc86bd-3770-5832-7fa5-d28856998ae6
• Version Independent ID: cbdb8c6f-ad4d-9e3d-a490-f1348b5ccdfa
• Content: Using SQL databases on Azure Stack
• Content Source: azure-stack/operator/azure-stack-sql-resource-provider-deploy.md
• Service: azure-stack
• GitHub Login: @jeffgilb
• Microsoft Alias: jeffgilb

In the release notes it is stated "BGP and NAT components are now deployed on the physical host. This eliminates the need to have two public or corporate IP addresses for deploying the ASDK, and also simplifies deployment."
Since networking is absolute key to get a cloud working it would be appreciated if there were some more info about how this change has been implemented.
We normally set up our ASDKs as routed installations (no VPN and such) so the new 1901 installation is proving to quite the handful to get to work.. :)
(yeah, i know that our way of installation isn't the normal, or probably even supported way. But the end customers LOVE it and it makes the barrier to get them to try it SO much lower)
//Bjorn Andersson, Visolit Sweden (previously known as "TeleComputing sweden")

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 0f8368a3-49e9-5216-f7cb-f91f6f1122c1
• Version Independent ID: 12092beb-efeb-974f-f9fe-5428435b228b
• Content: Microsoft Azure Stack Development Kit release notes
• Content Source: articles/azure-stack/asdk/asdk-release-notes.md
• Service: azure-stack
• GitHub Login: @sethmanheim
• Microsoft Alias: sethm

When I went to install version 1902, the screen shots have changed. Please update them to reflect the new screens.

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: e46293a4-00e4-46d5-d052-09f49c99d3c9
• Version Independent ID: 5df13a3e-3b6e-a90f-968e-72a5b5dc4447
• Content: Install the Azure Stack Development Kit (ASDK)
• Content Source: articles/azure-stack/asdk/asdk-install.md
• Service: azure-stack
• GitHub Login: @jeffgilb
• Microsoft Alias: jeffgilb

Are all products available on azure stack? I feel like I might be missing something super obvious.

Cheers,
Nick

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: e7365a8d-a66f-b338-117a-abbb49bb4db0
• Version Independent ID: 0e32791c-3fee-636f-27f6-37b08dfcd5b4
• Content: What is Azure Stack?
• Content Source: azure-stack/operator/azure-stack-overview.md
• Service: azure-stack
• GitHub Login: @mattbriggs
• Microsoft Alias: mabrigg

Deploy Kubernetes, Step "11. Enter the Service Principal Client Secret that you created when creating your service principal."

Service Principal Client Secret is not a mandatory field in the admin portal interface and no warning is presented if it is left blank, but this value is required for Azure AD (this doc) and the deployment will fail without it. Suggest updating this step to mention it is mandatory for Azure AD deployments. This was confirmed by PG.

This field is not mandatory because it is not required for AD FS deployment, which is covered in another doc.

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: b60c4726-881a-a32c-6a85-25ca65a31c00
• Version Independent ID: a40334b6-dca7-52f7-62c3-3b8ecba6d606
• Content: Deploy Kubernetes to Azure Stack using Azure Active Directory (Azure AD)
• Content Source: azure-stack/user/azure-stack-solution-template-kubernetes-azuread.md
• Service: azure-stack
• GitHub Login: @mattbriggs
• Microsoft Alias: mabrigg

Hello, we have a known issue on this release and previous ones that was never published: Unable to remove Scale Sets via the "Virtual Machine Scale Sets" blade in the portal. The Scale set's blade or PowerShell can be used as workaround. Can this be added to the known issues list? Thank you!

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: cfeb25b3-a85d-ac1f-1b2f-d7f95d8b196c
• Version Independent ID: 381939cb-8180-c365-6271-91522b6821b9
• Content: Azure Stack release notes - known issues in 1904
• Content Source: azure-stack/operator/azure-stack-release-notes-known-issues-1904.md
• Service: azure-stack
• GitHub Login: @sethmanheim
• Microsoft Alias: sethm

It may be necessary to modify the NTP configuration settings used in the deployment worksheet. The two cmdlets Get-AzSTimeSource and Set-AzSTimeSource exist on the privileged endpoints but are not documented. Suggest adding a paragraph to either the Network integration or Border connectivity page explaining how a cloud administrator can change the NTP source post-deployment. This issue has come up on several phone calls with Microsoft and OEM partners and it was unclear to either party how this could be done without breaking glass.

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 147eee4f-8b0f-927a-14ff-5642accb3610
• Version Independent ID: 95213ed3-d96f-8ad9-e442-7c7f29164ebb
• Content: Network integration considerations for Azure Stack integrated systems
• Content Source: articles/azure-stack/azure-stack-network.md
• Service: azure-stack
• GitHub Login: @jeffgilb
• Microsoft Alias: jeffgilb

Hi,

I have two versions of an item that I added from Azure into Azure Stack ADFS marketplace management. In Marketplace Management, I can see both items and the corresponding version. When I go to Marketplace, I only see one item. Since there is no version info, I don't know which item it corresponds to.

In the connected scenario, step 5 mentions: "To deploy the downloaded item, select + Create a resource, and then search among the categories for the new marketplace item. ".
Does it mean that when we are in Marketplace management page and select the item, we should see "Create a resource" somewhere? In my case, I don't have that option.

Thanks.

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: b5a0e40a-4042-9935-0f59-37eb87ec478e
• Version Independent ID: 81e5de2b-da67-e875-405d-65628be05adc
• Content: Download marketplace items from Azure
• Content Source: azure-stack/operator/azure-stack-download-azure-marketplace-item.md
• Service: azure-stack
• GitHub Login: @sethmanheim
• Microsoft Alias: sethm

Hello, Would it be possible to add a clarification on the need to download new version of Windows Server images? It is not clear to me if the images downloaded are automatically updated with the new OS fixes and new versions of guest OS, or if the admin must manually replace the images periodically to have the latest updates available. Thank you!

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 2945c53e-1796-2a51-7de8-55b6289f319c
• Version Independent ID: a879ecd5-7baa-c3d1-4197-863124c6978c
• Content: Azure Marketplace items available for Azure Stack
• Content Source: articles/azure-stack/azure-stack-marketplace-azure-items.md
• Service: azure-stack
• GitHub Login: @sethmanheim
• Microsoft Alias: sethm

It may be necessary to modify the NTP configuration settings used in the deployment worksheet. The two cmdlets Get-AzSTimeSource and Set-AzSTimeSource exist on the privileged endpoints but are not documented. Suggest adding a paragraph to either the Network integration or Border connectivity page explaining how a cloud administrator can change the NTP source post-deployment. This issue has come up on several phone calls with Microsoft and OEM partners and it was unclear to either party how this could be done without breaking glass.

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 147eee4f-8b0f-927a-14ff-5642accb3610
• Version Independent ID: 97898f74-ff92-0557-a3c7-35c4df372706
• Content: Network integration considerations for Azure Stack integrated systems
• Content Source: articles/azure-stack/azure-stack-network.md
• Service: azure-stack
• GitHub Login: @jeffgilb
• Microsoft Alias: jeffgilb

Because Azure RM powershell 2.4.0 version doesn't allow to use hybrid profile, Azure RM powershell 2.3.0 should be used with custom script deployment. Additionaly, since Azure Stack powershell 1.7.0 is incompatible with Azure RM 2.3.0, Azure Stack powershell 1.5.0 or 1.6.0 must be used in conjunction with Azure RM 2.3.0.

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 2c085e86-242e-ac36-a611-3d379d3dcfb0
• Version Independent ID: 4d455fad-dc6a-ed4f-75c0-f8a6118aa07a
• Content: Before you deploy App Service on Azure Stack
• Content Source: azure-stack/operator/azure-stack-app-service-before-you-get-started.md
• Service: azure-stack
• GitHub Login: @jeffgilb
• Microsoft Alias: anwestg

Under the section Enable backup on 1901 and beyond using certificate, it seems like there is a mismatch on the path location and the name of the cert file. after creating the cert, it is then exported to the directory called "certs" on the C: drive. Then when running the final line of code the encryptioncertpath is set to c:\temp\cert.cer
this is confusing as in the earlier portion of code the cert was exported and saved as "AzSIBCCert.cer". I then changed path to c:\certs\AzSIBCCert.cer and the final line of code worked but now I get a failed backup warning when trying the "BackUp Now" through the admin portal. am I missing something or overlooking a step?

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 25dd0267-d611-f945-3008-a036315185d8
• Version Independent ID: db61f61a-200f-0b72-7bfc-3c33a97ecefe
• Content: Enable Backup for Azure Stack with PowerShell
• Content Source: articles/azure-stack/azure-stack-backup-enable-backup-powershell.md
• Service: azure-stack
• GitHub Login: @jeffgilb
• Microsoft Alias: jeffgilb

[Enter feedback here]
Hello.
The current latest SQL RP requires:
Use-AzureRmProfile -Profile 2018-03-01-hybrid
Install-Module -Name AzureStack -RequiredVersion 1.5.0

The core Azure Stack 1902 release requires:
Install-Module AzureRM -RequiredVersion 2.4.0
Install-Module -Name AzureStack -RequiredVersion 1.7.0

Please advise when a new SQL RP will be made available for the 1902 build.

Here is the error:
Azure Powershell Module with 2.4.0 version found. Need Azure powershell compatible with stack. Use ArmProfile 2018-03-01-hybrid. Please uninstall the current version and rerun the RP setup

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 31804a1d-4c4f-70e6-556c-66c533e9b3e3
• Version Independent ID: cbdb8c6f-ad4d-9e3d-a490-f1348b5ccdfa
• Content: Using SQL databases on Azure Stack
• Content Source: articles/azure-stack/azure-stack-sql-resource-provider-deploy.md
• Service: azure-stack
• GitHub Login: @jeffgilb
• Microsoft Alias: jeffgilb

The command provided to rollback ADFS integration is "Reset-DatacenterIntegrationConfiguration" but in the Privileged Endpoint it is actually misspelled. The PEP has it listed as "Reset-DatacenterIntegationConfiguration".

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: d295c322-0813-e159-e6f8-86f04b759c48
• Version Independent ID: 02b87d3f-125b-d674-b750-79dbaee5e497
• Content: Azure Stack datacenter integration - Identity
• Content Source: azure-stack/operator/azure-stack-integrate-identity.md
• Service: azure-stack
• GitHub Login: @PatAltimore
• Microsoft Alias: patricka

I really appreciate how well it is all laid out. Feel free to close. Just a quick kudo

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 517b1814-7971-258a-1e6e-cfd0769d3fbc
• Version Independent ID: e2eb938a-1a20-d94b-63d6-c8b66f1a8dad
• Content: Capacity planning for Azure Stack
• Content Source: azure-stack/operator/capacity-planning.md
• Service: azure-stack
• GitHub Login: @mattbriggs
• Microsoft Alias: mabrigg

• The relevant Azure service or technology: Azure Stack virtual networking concepts

• A link to the published documentation article that you have feedback about.:
  https://github.com/MicrosoftDocs/azure-stack-docs/blob/master/azure-stack/operator/azure-stack-network.md
  https://github.com/MicrosoftDocs/azure-stack-docs/blob/master/azure-stack/operator/azure-stack-connect-expressroute.md

• Clear, specific feedback that the author can act on.
  The documentations/diagrams related to virtual network devices do not use consistent naming or topology which leads to confusion. What is the correct traffic flow and terminology for traffic routing to device on public networks (Public VIPs). For example this is the various naming and topology referred to across various documents and diagram:

• SDN | Software BGP ASN : https://github.com/MicrosoftDocs/azure-stack-docs/blob/master/azure-stack/operator/media/azure-stack-network/NetworkDiagram.png

• Load Balancer : https://github.com/MicrosoftDocs/azure-stack-docs/blob/master/azure-stack/operator/media/azure-stack-connect-expressroute/Conceptual.png

• NAT | Multitenant Gateway: https://github.com/MicrosoftDocs/azure-stack-docs/blob/master/azure-stack/operator/media/azure-stack-connect-expressroute/Architecture.png

• NAT/FW | SLB | Multitenant Gateway: https://github.com/MicrosoftDocs/azure-stack-docs/blob/master/azure-stack/operator/media/azure-stack-connect-expressroute/EndToEnd.png

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 147eee4f-8b0f-927a-14ff-5642accb3610
• Version Independent ID: 95213ed3-d96f-8ad9-e442-7c7f29164ebb
• Content: Network integration considerations for Azure Stack integrated systems
• Content Source: articles/azure-stack/azure-stack-network.md
• Service: azure-stack
• GitHub Login: @jeffgilb
• Microsoft Alias: jeffgilb

The table Capabilities and Limitations is outdated.

Azure Stack release 1811 introduced this capability:

• Added support for Service Principals using a client secret with Active Directory Federated Services (AD FS).

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 013a0f43-0887-69dd-b02f-cb3cddaedd3f
• Version Independent ID: cb5673ae-2a4b-513f-fb26-5ccd58d8d0d2
• Content: Identity architecture for Azure Stack
• Content Source: articles/azure-stack/azure-stack-identity-architecture.md
• Service: azure-stack
• GitHub Login: @PatAltimore
• Microsoft Alias: patricka

Container name does not accept upper case, so that example should be lower case on step 4.

"Under Blob service, select + Container to create a container. Enter a name (for example Update-1811), and then select OK.

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: ae1fb775-13ec-28b6-060d-af8f601d18c0
• Version Independent ID: 6225e89d-4bc4-8232-34ae-b479ded1a1b0
• Content: Apply updates in Azure Stack
• Content Source: azure-stack/operator/azure-stack-apply-updates.md
• Service: azure-stack
• GitHub Login: @mattbriggs
• Microsoft Alias: mabrigg

Hi Team,

Parameter "-intent" no longer available - Concerned part: "Identify the best destination shares to hold the container you migrate" in https://docs.microsoft.com/en-us/azure-stack/operator/azure-stack-manage-storage-shares

Thank you!

Regards,

Hailian Li

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 03c63388-ff19-a72e-959b-883a01b400e8
• Version Independent ID: bba686d4-1463-c9a1-bdb4-7d3edf095fee
• Content: Manage storage capacity in Azure Stack
• Content Source: azure-stack/operator/azure-stack-manage-storage-shares.md
• Service: azure-stack
• GitHub Login: @mattbriggs
• Microsoft Alias: mabrigg

In the static routing section, all of the P2P references used are singular in nature. e.g.:
In the text: "static routes pointing to the TOR devices P2P"
In the image: "Customer border assign static route to TOR P2P"

In a static routing scenario, the TOR device (or devices) should always have multiple uplinks (as shown in the image) and therefore should always have multiple P2P connections. If a customer took the singular reference literally and only configured a route to one of the P2P connections, in the cases where the Azure Stack TORs chose one of the other available paths, network communication would fail.

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: aaa29c6e-0845-f9e9-1f79-af2dea1081c4
• Version Independent ID: b0e0e929-6ccc-f0bb-7814-8962efed9e98
• Content: Border connectivity network integration considerations for Azure Stack integrated systems
• Content Source: articles/azure-stack/azure-stack-border-connectivity.md
• Service: azure-stack
• GitHub Login: @jeffgilb
• Microsoft Alias: jeffgilb

This doc addresses creating custom worker tiers, but not how to remove them. Recomment adding a section on removing them, including this cmdlet, which does not appear to be documented anywhere...

Remove-AppServiceWorkerTier -WorkerSize -ComputeMode

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: ba102ce6-c79f-33fe-fadb-a77a4c5cdd8f
• Version Independent ID: c38cb661-e97f-8bf1-4c48-1b5c1359b856
• Content: Scale out worker roles in App Services - Azure Stack
• Content Source: articles/azure-stack/azure-stack-app-service-add-worker-roles.md
• Service: azure-stack
• GitHub Login: @apwestgarth
• Microsoft Alias: anwestg