You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/cloud-services-extended-support/deploy-portal.md
+8-6Lines changed: 8 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,15 +17,17 @@ This article shows you how to use the Azure portal to create an Azure Cloud Serv
17
17
18
18
Review the [deployment prerequisites](deploy-prerequisite.md) for Cloud Services (extended support) and create the required resources.
19
19
20
-
## Deploy Cloud Services (extended support) in the portal
20
+
## Deploy Cloud Services (extended support)
21
+
22
+
To deploy Cloud Services (extended support) by using the portal:
21
23
22
24
1. Sign in to the [Azure portal](https://portal.azure.com).
23
25
24
26
1. In the search bar, enter **Cloud Services (extended support)**, and then select it in the search results.
25
27
26
28
:::image type="content" source="media/deploy-portal-1.png" alt-text="Screenshot that shows a Cloud Services (extended support) search in the Azure portal, and selecting the result.":::
27
29
28
-
1. On the **Cloud Services (extended support)** services pane, select **Create**.
30
+
1. On the **Cloud services (extended support)** services pane, select **Create**.
29
31
30
32
:::image type="content" source="media/deploy-portal-2.png" alt-text="Screenshot that shows selecting Create in the menu to create a new instance of Cloud Services (extended support).":::
31
33
@@ -41,7 +43,7 @@ Review the [deployment prerequisites](deploy-prerequisite.md) for Cloud Services
1. On the **Basics** tab under **Cloud service configuration, package, and service definition**, add your package (.cspkg or .zip) file, configuration (.cscfg) file, and definition (.csdef) file for the deployment. You can add existing files from blob storage or upload the files from your local machine. If you upload the files from your local machine, the files are stored in a storage account in Azure.
46
+
1. On the **Basics** tab under **Cloud service configuration, package, and service definition**, add your package (.cspkg or .zip) file, configuration (.cscfg) file, and definition (.csdef) file for the deployment. You can add existing files from blob storage or upload the files from your local machine. If you upload the files from your local machine, the files are then stored in a storage account in Azure.
45
47
46
48
:::image type="content" source="media/deploy-portal-4.png" alt-text="Screenshot that shows the section of the Basics tab where you upload files and select storage.":::
47
49
@@ -54,13 +56,13 @@ Review the [deployment prerequisites](deploy-prerequisite.md) for Cloud Services
54
56
55
57
-**Public IP**: Select an existing public IP address to associate with the cloud service, or create a new one.
56
58
57
-
- If you have IP input endpoints defined in your service definition (.csdef) file, create a public IP address for your cloud service.
59
+
- If you have IP input endpoints defined in your definition (.csdef) file, create a public IP address for your cloud service.
58
60
- Cloud Services (extended support) supports only a Basic SKU public IP address.
59
61
- If your configuration (.cscfg) file contains a reserved IP address, set the allocation type for the public IP address to **Static**.
60
-
- (Optional). You can assign a DNS name for your cloud service endpoint by updating the DNS label property of the public IP address associated with the cloud service.
62
+
- (Optional) You can assign a DNS name for your cloud service endpoint by updating the DNS label property of the public IP address that's associated with the cloud service.
61
63
- (Optional) **Start cloud service**: Select the checkbox if you want to start the service immediately after it's deployed.
62
64
-**Key vault**: Select a key vault.
63
-
- A key vault is required when you specify one or more certificates in your configuration (.cscfg) file. When you select a key vault, we attempt to find the selected certificates that are defined in your configuration (.cscfg) file based on the certificate thumbprints. If any certificates are missing from your key vault, you can upload them, and then select **Refresh**.
65
+
- A key vault is required when you specify one or more certificates in your configuration (.cscfg) file. When you select a key vault, we attempt to find the selected certificates that are defined in your configuration (.cscfg) file based on the certificate thumbprints. If any certificates are missing from your key vault, you can upload them now , and then select **Refresh**.
64
66
65
67
:::image type="content" source="media/deploy-portal-5.png" alt-text="Screenshot that shows the Configuration tab in the Azure portal when you create a Cloud Services (extended support) deployment.":::
## Deploy Cloud Services (extended support) by using PowerShell
42
+
## Deploy Cloud Services (extended support)
43
43
44
-
Use any of the following Azure PowerShell cmdlets to deploy Cloud Services (extended support):
44
+
Use any of the following PowerShell cmdlet options to deploy Cloud Services (extended support):
45
45
46
46
- Quick-create a deployment by using a [storage account](#quick-create-a-deployment-by-using-a-storage-account)
47
47
@@ -51,18 +51,18 @@ Use any of the following Azure PowerShell cmdlets to deploy Cloud Services (exte
51
51
52
52
- Quick-create a deployment by using a [shared access signature URI](#quick-create-a-deployment-by-using-an-sas-uri)
53
53
54
-
- This parameter set inputs the shared access signature (SAS) URI of the package (.cspkg) file with the local paths to the configuration (.cscfg) file and definition (.csdef) file. No storage account input is required.
54
+
- This parameter set inputs the shared access signature (SAS) URI of the package (.cspkg or .zip) file with the local paths to the configuration (.cscfg) file and definition (.csdef) file. No storage account input is required.
55
55
- The cloud service role profile, network profile, and OS profile are created by the cmdlet with minimal input.
56
56
- To input a certificate, you must specify a key vault name. The certificate thumbprints in the key vault are validated against the certificates that you specify in the configuration (.cscfg) file for the deployment.
57
57
58
58
- Create a deployment by using a [role profile, OS profile, network profile, and extension profile with shared access signature URIs](#create-a-deployment-by-using-profile-objects-and-sas-uris)
59
59
60
-
- This parameter set inputs the SAS URIs of the package (.cspkg) file and configuration (.cscfg) file.
60
+
- This parameter set inputs the SAS URIs of the package (.cspkg or .zip) file and configuration (.cscfg) file.
61
61
- You must specify profile objects: role profile, network profile, OS profile, and extension profile. The profiles must match the values that you set in the configuration (.cscfg) file and definition (.csdef) file.
62
62
63
63
### Quick-create a deployment by using a storage account
64
64
65
-
Create a Cloud Services (extended support) deployment by using the package (.cspkg) file, configuration (.cscfg) file, and definition (.csdef) files:
65
+
Create a Cloud Services (extended support) deployment by using the package (.cspkg or .zip) file, configuration (.cscfg) file, and definition (.csdef) files:
66
66
67
67
```azurepowershell-interactive
68
68
$cspkgFilePath = "<Path to .cspkg file>"
@@ -83,7 +83,7 @@ New-AzCloudService
83
83
84
84
### Quick-create a deployment by using an SAS URI
85
85
86
-
1. Upload the package (.cspkg) file for the deployment to the storage account:
86
+
1. Upload the package (.cspkg or .zip) file for the deployment to the storage account:
87
87
88
88
```azurepowershell-interactive
89
89
$tokenStartTime = Get-Date
@@ -95,7 +95,7 @@ New-AzCloudService
95
95
$csdefFilePath = "<Path to csdef file>"
96
96
```
97
97
98
-
1. Create the Cloud Services (extended support) deployment by using the package (.cspkg) file, configuration (.cscfg) file, and definition (.csdef) file SAS URI:
98
+
1. Create the Cloud Services (extended support) deployment by using the package (.cspkg or .zip) file, configuration (.cscfg) file, and definition (.csdef) file SAS URI:
1. Th following example adds a self-signed certificate to a key vault. You must add the certificate thumbprint via the configuration (.cscfg) file for Cloud Services (extended support) roles.
174
+
1. The following example adds a self-signed certificate to a key vault. You must add the certificate thumbprint via the configuration (.cscfg) file for Cloud Services (extended support) roles.
1. Create a role profile in-memory object. A role profile defines a role SKU-specific properties such as name, capacity, and tier. In this example, two roles are defined: frontendRole and backendRole. Role profile information must match the role configuration that's defined in the deployment configuration (.cscfg) file and definition (.csdef) file.
190
+
1. Create a role profile in-memory object. A role profile defines a role's SKU-specific properties such as name, capacity, and tier. In this example, two roles are defined: frontendRole and backendRole. Role profile information must match the role configuration that's defined in the deployment configuration (.cscfg) file and definition (.csdef) file.
This article shows how to use the [Azure SDK](https://azure.microsoft.com/downloads/) to create an Azure Cloud Services (extended support) deployment that has multiple roles (WebRole and WorkerRole) and the Remote Desktop Protocol (RDP) extension. Cloud Services (extended support) is a deployment model of Azure Cloud Services that's based on Azure Resource Manager.
16
16
17
-
## Before you begin
17
+
## Prerequisites
18
18
19
19
Review the [deployment prerequisites](deploy-prerequisite.md) for Cloud Services (extended support) and create the required resources.
20
20
21
-
## Deploy Cloud Services (extended support) by using the SDK
21
+
## Deploy Cloud Services (extended support)
22
+
23
+
To deploy Cloud Services (extended support) by using the SDK:
22
24
23
25
1. Install the [Azure Compute SDK NuGet package](https://www.nuget.org/packages/Microsoft.Azure.Management.Compute/43.0.0-preview) and initialize the client by using a standard authentication method:
24
26
@@ -67,7 +69,7 @@ Review the [deployment prerequisites](deploy-prerequisite.md) for Cloud Services
1. Createastorageaccountandcontainerwhereyou'll store the package (.cspkg) file and configuration (.cscfg) file for the deployment. Install the [Azure Storage NuGet package](https://www.nuget.org/packages/Azure.Storage.Common/). This step is optional if you'reusinganexistingstorageaccount. Thestorageaccountnamemustbeunique.
72
+
1. Createastorageaccountandcontainerwhereyou'll store the package (.cspkg or .zip) file and configuration (.cscfg) file for the deployment. Install the [Azure Storage NuGet package](https://www.nuget.org/packages/Azure.Storage.Common/). This step is optional if you'reusinganexistingstorageaccount. Thestorageaccountnamemustbeunique.
71
73
72
74
```csharp
73
75
stringstorageAccountName= “ContosoSAS”
@@ -208,13 +210,13 @@ Review the [deployment prerequisites](deploy-prerequisite.md) for Cloud Services
Copy file name to clipboardExpand all lines: articles/cloud-services-extended-support/deploy-template.md
+12-10Lines changed: 12 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,12 +27,14 @@ Complete the following steps as prerequisites to creating your deployment by usi
27
27
28
28
1. (Optional) Create a key vault and upload the certificates.
29
29
30
-
- You can attach certificates to your deployment for secure communication to and from the service. If you use certificate, the certificate thumbprints must be specified in your configuration (.cscfg) file and be uploaded to a key vault. You can create a key vault by using the [Azure portal](../key-vault/general/quick-create-portal.md) or [Azure PowerShell](../key-vault/general/quick-create-powershell.md).
31
-
- The associated key vault must be located in the same region and subscription as your Cloud Services (extended support) deployment.
32
-
- The associated key vault must have the relevant permissions so that Cloud Services (extended support) resources can retrieve certificates from the key vault. For more information, see [Use certificates with Cloud Services (extended support](certificates-and-key-vault.md).
30
+
- You can attach certificates to your deployment for secure communication to and from the service. If you use certificates, the certificate thumbprints must be specified in your configuration (.cscfg) file and be uploaded to a key vault. You can create a key vault by using the [Azure portal](../key-vault/general/quick-create-portal.md) or [Azure PowerShell](../key-vault/general/quick-create-powershell.md).
31
+
- The associated key vault must be in the same region and subscription as your Cloud Services (extended support) deployment.
32
+
- The associated key vault must have the relevant permissions so that Cloud Services (extended support) resources can retrieve certificates from the key vault. For more information, see [Use certificates with Cloud Services (extended support)](certificates-and-key-vault.md).
33
33
- The key vault must be referenced in the `osProfile` section of the ARM template as shown in a later step.
34
34
35
-
## Deploy Cloud Services (extended support) by using a template
35
+
## Deploy Cloud Services (extended support)
36
+
37
+
To deploy Cloud Services (extended support) by using a template:
36
38
37
39
> [!NOTE]
38
40
> An easier and faster way to generate your ARM template and parameter file is by using the [Azure portal](https://portal.azure.com). You can [download the generated ARM template](generate-template-portal.md) in the portal to create your Cloud Services (extended support) via Azure PowerShell.
@@ -73,7 +75,7 @@ Complete the following steps as prerequisites to creating your deployment by usi
73
75
]
74
76
```
75
77
76
-
1. Create a public IP address and (optionally) set the DNS label property of the public IP address. If you use a static IP address, you must reference it as a reserved IP address in the configuration (.cscfg) file. If you use an existing IP address, skip this step and add the IP address information directly in the load balancer configuration settings of your ARM template.
78
+
1. Create a public IP address and (optionally) set the DNS label property of the public IP address. If you use a static IP address, you must reference it as a reserved IP address in the configuration (.cscfg) file. If you use an existing IP address, skip this step and add the IP address information directly in the load balancer configuration settings in your ARM template.
77
79
78
80
```json
79
81
"resources": [
@@ -208,11 +210,11 @@ Complete the following steps as prerequisites to creating your deployment by usi
208
210
> [!NOTE]
209
211
> The password for RDP must from 8 to 123 characters and must satisfy at least *three* of the following password-complexity requirements:
0 commit comments