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/cloud-services-certs-create.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -50,7 +50,7 @@ You can use any tool available to create a self-signed certificate as long as th
50
50
* Created for key exchange (.pfx file).
51
51
* Subject name must match the domain used to access the cloud service.
52
52
53
-
> You cannot acquire an SSL certificate for the cloudapp.net (or for any Azure-related) domain; the certificate's subject name must match the custom domain name used to access your application. For example, **contoso.net**, not **contoso.cloudapp.net**.
53
+
> You cannot acquire a TLS/SSL certificate for the cloudapp.net (or for any Azure-related) domain; the certificate's subject name must match the custom domain name used to access your application. For example, **contoso.net**, not **contoso.cloudapp.net**.
54
54
55
55
* Minimum of 2048-bit encryption.
56
56
***Service Certificate Only**: Client-side certificate must reside in the *Personal* certificate store.
Copy file name to clipboardExpand all lines: articles/cloud-services/cloud-services-configure-ssl-certificate-portal.md
+9-9Lines changed: 9 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
-
title: Configure SSL for a cloud service | Microsoft Docs
3
-
description: Learn how to specify an HTTPS endpoint for a web role and how to upload an SSL certificate to secure your application. These examples use the Azure portal.
2
+
title: Configure TLS for a cloud service | Microsoft Docs
3
+
description: Learn how to specify an HTTPS endpoint for a web role and how to upload a TLS/SSL certificate to secure your application. These examples use the Azure portal.
4
4
services: cloud-services
5
5
documentationcenter: .net
6
6
author: tgore03
@@ -10,9 +10,9 @@ ms.date: 05/26/2017
10
10
ms.author: tagore
11
11
12
12
---
13
-
# Configuring SSL for an application in Azure
13
+
# Configuring TLS for an application in Azure
14
14
15
-
Secure Socket Layer (SSL) encryption is the most commonly used method of securing data sent across the internet. This common task discusses how to specify an HTTPS endpoint for a web role and how to upload an SSL certificate to secure your application.
15
+
Transport Layer Security (TLS), previously known as Secure Socket Layer (SSL) encryption, is the most commonly used method of securing data sent across the internet. This common task discusses how to specify an HTTPS endpoint for a web role and how to upload a TLS/SSL certificate to secure your application.
16
16
17
17
> [!NOTE]
18
18
> The procedures in this task apply to Azure Cloud Services; for App Services, see [this](../app-service/configure-ssl-bindings.md).
@@ -22,14 +22,14 @@ This task uses a production deployment. Information on using a staging deploymen
22
22
23
23
Read [this](cloud-services-how-to-create-deploy-portal.md) first if you have not yet created a cloud service.
24
24
25
-
## Step 1: Get an SSL certificate
26
-
To configure SSL for an application, you first need to get an SSL certificate that has been signed by a Certificate Authority (CA), a trusted third party who issues certificates for this purpose. If you do not already have one, you need to obtain one from a company that sells SSL certificates.
25
+
## Step 1: Get a TLS/SSL certificate
26
+
To configure TLS for an application, you first need to get a TLS/SSL certificate that has been signed by a Certificate Authority (CA), a trusted third party who issues certificates for this purpose. If you do not already have one, you need to obtain one from a company that sells TLS/SSL certificates.
27
27
28
-
The certificate must meet the following requirements for SSL certificates in Azure:
28
+
The certificate must meet the following requirements for TLS/SSL certificates in Azure:
29
29
30
30
* The certificate must contain a private key.
31
31
* The certificate must be created for key exchange, exportable to a Personal Information Exchange (.pfx) file.
32
-
* The certificate's subject name must match the domain used to access the cloud service. You cannot obtain an SSL certificate from a certificate authority (CA) for the cloudapp.net domain. You must acquire a custom domain name to use when access your service. When you request a certificate from a CA, the certificate's subject name must match the custom domain name used to access your application. For example, if your custom domain name is **contoso.com** you would request a certificate from your CA for ***.contoso.com** or **www\.contoso.com**.
32
+
* The certificate's subject name must match the domain used to access the cloud service. You cannot obtain a TLS/SSL certificate from a certificate authority (CA) for the cloudapp.net domain. You must acquire a custom domain name to use when access your service. When you request a certificate from a CA, the certificate's subject name must match the custom domain name used to access your application. For example, if your custom domain name is **contoso.com** you would request a certificate from your CA for ***.contoso.com** or **www\.contoso.com**.
33
33
* The certificate must use a minimum of 2048-bit encryption.
34
34
35
35
For test purposes, you can [create](cloud-services-certs-create.md) and use a self-signed certificate. A self-signed certificate is not authenticated through a CA and can use the cloudapp.net domain as the website URL. For example, the following task uses a self-signed certificate in which the common name (CN) used in the certificate is **sslexample.cloudapp.net**.
> If you want to use SSL for a staging deployment instead of a production deployment, you'll first need to determine the URL used for the staging deployment. Once your cloud service has been deployed, the URL to the staging environment is determined by the **Deployment ID** GUID in this format: `https://deployment-id.cloudapp.net/`
179
+
> If you want to use TLS for a staging deployment instead of a production deployment, you'll first need to determine the URL used for the staging deployment. Once your cloud service has been deployed, the URL to the staging environment is determined by the **Deployment ID** GUID in this format: `https://deployment-id.cloudapp.net/`
180
180
>
181
181
> Create a certificate with the common name (CN) equal to the GUID-based URL (for example, **328187776e774ceda8fc57609d404462.cloudapp.net**). Use the portal to add the certificate to your staged cloud service. Then, add the certificate information to your CSDEF and CSCFG files, repackage your application, and update your staged deployment to use the new package.
Copy file name to clipboardExpand all lines: articles/cloud-services/cloud-services-custom-domain-name-portal.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,7 +25,7 @@ Do you already understand what CNAME and A records are? [Jump past the explanati
25
25
<p/>
26
26
27
27
> [!TIP]
28
-
> Get going faster--use the NEW Azure [guided walkthrough](https://support.microsoft.com/kb/2990804)! It makes associating a custom domain name AND securing communication (SSL) with Azure Cloud Services or Azure Websites a snap.
28
+
> Get going faster--use the NEW Azure [guided walkthrough](https://support.microsoft.com/kb/2990804)! It makes associating a custom domain name AND securing communication (TLS) with Azure Cloud Services or Azure Websites a snap.
29
29
>
30
30
>
31
31
@@ -125,7 +125,7 @@ This example demonstrates creating an A record for the root domain. If you wish
125
125
* [How to Map CDN Content to a Custom Domain](../cdn/cdn-map-content-to-custom-domain.md)
126
126
* [General configuration of your cloud service](cloud-services-how-to-configure-portal.md).
127
127
* Learn how to [deploy a cloud service](cloud-services-how-to-create-deploy-portal.md).
Copy file name to clipboardExpand all lines: articles/cloud-services/cloud-services-how-to-create-deploy-portal.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -37,7 +37,7 @@ Before you can deploy a cloud service, you must create the cloud service package
37
37
38
38
Three cloud service features require special configurations before you export a service package:
39
39
40
-
* If you want to deploy a cloud service that uses Secure Sockets Layer (SSL) for data encryption, [configure your application](cloud-services-configure-ssl-certificate-portal.md#modify) for SSL.
40
+
* If you want to deploy a cloud service that uses Transport Layer Security (TLS), previously known as Secure Sockets Layer (SSL), for data encryption, [configure your application](cloud-services-configure-ssl-certificate-portal.md#modify) for TLS.
41
41
* If you want to configure Remote Desktop connections to role instances, [configure the roles](cloud-services-role-enable-remote-desktop-new-portal.md) for Remote Desktop.
42
42
* If you want to configure verbose monitoring for your cloud service, enable Azure Diagnostics for the cloud service. *Minimal monitoring* (the default monitoring level) uses performance counters gathered from the host operating systems for role instances (virtual machines). *Verbose monitoring* gathers additional metrics based on performance data within the role instances to enable closer analysis of issues that occur during application processing. To find out how to enable Azure Diagnostics, see [Enabling diagnostics in Azure](cloud-services-dotnet-diagnostics.md).
43
43
@@ -65,7 +65,7 @@ To create a cloud service with deployments of web roles or worker roles, you mus
65
65
## Upload a certificate
66
66
If your deployment package was [configured to use certificates](cloud-services-configure-ssl-certificate-portal.md#modify), you can upload the certificate now.
67
67
68
-
1. Select **Certificates**, and on the **Add certificates** pane, select the SSL certificate .pfx file, and then provide the **Password** for the certificate,
68
+
1. Select **Certificates**, and on the **Add certificates** pane, select the TLS/SSL certificate .pfx file, and then provide the **Password** for the certificate,
69
69
2. Click **Attach certificate**, and then click **OK** on the **Add certificates** pane.
70
70
3. Click **Create** on the **Cloud Service** pane. When the deployment has reached the **Ready** status, you can proceed to the next steps.
71
71
@@ -85,7 +85,7 @@ If your deployment package was [configured to use certificates](cloud-services-c
85
85
*[General configuration of your cloud service](cloud-services-how-to-configure-portal.md).
86
86
* Configure a [custom domain name](cloud-services-custom-domain-name-portal.md).
87
87
*[Manage your cloud service](cloud-services-how-to-manage-portal.md).
0 commit comments