Merge pull request #20 from unic/feature/add-step-for-Azure-package-i…

…n-creating-a-release-doc

add step for Azure package in creating a release doc

be/docs/README.md

@@ -158,6 +158,13 @@ ConvertTo-SCModuleWebDeployPackage "<path-to-installation-package>\UrlMapper2_CD
 ConvertTo-SCModuleWebDeployPackage "<path-to-installation-package>\UrlMapper2_CM-<version>.zip" "<output-path>"
 ```
 
+> Packages generated by Sitecore Azure Toolkit don't really follow the Microsoft standards in the `parameters.xml` file, since they define a `Application Path` parameter containing the application name instead of the standard `IIS Web Application Name` parameters. In order to make the packages work with the default IIS Deployment and Azure App Service deployment tasks, the `parameters.xml` needs to be adjusted accordingly and injected into the packages.
+
+You can adjust the `parameters.xml` using the `Update-SCWebDeployPackage` cmdlet as follows:
+```powershell
+Update-SCWebDeployPackage -Path "<path-to-scwdp>" -ParametersXmlPath "<path-to-parameters-xml>"
+```
+
 Please note that if you are planning to use the modules for local or on-prem installations, you will have to disable dacpac options, which can be accomplished as follows:
 
 ```powershell