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
# Custom domain names and free managed certificates in Azure Container Apps
15
15
16
-
Azure Container Apps allows you to bind one or more custom domains to a container app. You can automatically configure a free managed certificate for your custom domain.
16
+
Azure Container Apps allows you to bind one or more custom domains to a container app. You can automatically configure a free managed certificate for your custom domain when your container app is publicly accessible.
17
17
18
18
If you want to set up a custom domain using your own certificate, see [Custom domain names and certificates in Azure Container Apps](custom-domains-certificates.md).
19
19
@@ -177,10 +177,8 @@ Container Apps supports apex domains and subdomains. Each domain type requires a
177
177
--query "properties.customDomainVerificationId"
178
178
```
179
179
180
-
1. Using the DNS provider that is hosting your domain, create DNS records based on the record type you selected using the values shown in the *Domain validation* section. The records point the domain to your container app and verify that you own it. The setup depends on whether you're using custom domains with the private endpoint (preview) feature:
180
+
1. Using the DNS provider that is hosting your domain, create DNS records based on the record type you selected using the values shown in the *Domain validation* section. The records point the domain to your container app and verify that you own it.
181
181
182
-
# [General](#tab/general)
183
-
184
182
- If you selected *A record*, create the following DNS records:
185
183
186
184
| Record type | Host | Value |
@@ -195,26 +193,6 @@ Container Apps supports apex domains and subdomains. Each domain type requires a
195
193
| CNAME | The subdomain (for example, `www`) | The generated domain of your container app. |
196
194
| TXT | `asuid.` followed by the subdomain (for example, `asuid.www`) | The domain verification code. |
197
195
198
-
# [Private endpoint](#tab/private-endpoint)
199
-
200
-
When using a private endpoint for your incoming traffic, you need to [create a private DNS zone](how-to-use-private-endpoint.md#configure-the-private-dns-zone).
201
-
202
-
- If you selected *A record*, create the following DNS records:
203
-
204
-
| Record type | Host | Value |
205
-
|--|--|--|
206
-
| A | `@` | The Private IP of your private endpoint on your container apps environment. |
207
-
| TXT | `asuid` | The domain verification code. |
208
-
209
-
- If you selected *CNAME*, create the following DNS records:
210
-
211
-
| Record type | Host | Value |
212
-
|--|--|--|
213
-
| CNAME | The subdomain (for example, `www`) | The generated domain of your container app. |
214
-
| TXT | `asuid.` followed by the subdomain (for example, `asuid.www`) | The domain verification code. |
Copy file name to clipboardExpand all lines: articles/cost-management-billing/costs/overview-cost-management.md
-1Lines changed: 0 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -66,7 +66,6 @@ For more information about supported offers, what data is included, or how data
66
66
67
67
During your cloud journey, there are many tools available to help you understand pricing:
68
68
69
-
- The [Total Cost of Ownership (TCO) calculator](https://azure.microsoft.com/pricing/tco/calculator/) should be your first stop if you’re curious about how much it would cost to move your existing on-premises infrastructure to the cloud.
70
69
-[Azure Migrate](https://azure.microsoft.com/products/azure-migrate/) is a free tool that helps you analyze your on-premises workloads and plan your cloud migration.
71
70
- The [Azure pricing calculator](https://azure.microsoft.com/pricing/calculator/) is a free cost management tool that allows users to understand and estimate costs of Azure Services and products. It serves as the only unauthenticated experience that allows you to configure and budget the expected cost of deploying solutions in Azure. For customers that want to view their negotiated estimate prices, there is an authenticated version. The Azure pricing calculator allows organizations to plan and forecast cloud expenses, evaluate different configurations and pricing models, and make informed decisions about service selection and deployment options.
4. The IoT Edge runtime uses AMQP by default to communicate with IoT Hub. Some proxy servers block AMQP ports. If that's the case, then you also need to configure edgeAgent to use AMQP over WebSocket. Remove the comment from the `UpstreamProtocol` parameter.
@@ -225,9 +225,9 @@ This step takes place once on the IoT Edge device during initial device setup.
4. The IoT Edge runtime uses AMQP by default to talk to IoT Hub. Some proxy servers block AMQP ports. If that's the case, then you also need to configure edgeAgent to use AMQP over WebSocket. Uncomment the `UpstreamProtocol` parameter.
@@ -253,9 +253,9 @@ This step takes place once on the IoT Edge device during initial device setup.
The Azure IoT Edge runtime is what turns a device into an IoT Edge device. The runtime can be deployed on devices as small as a Raspberry Pi or as large as an industrial server. Once a device is configured with the IoT Edge runtime, you can start deploying business logic to it from the cloud.
16
+
The Azure IoT Edge runtime turns a device into an IoT Edge device. You can deploy the runtime on devices as small as a Raspberry Pi or as large as an industrial server. After you set up the IoT Edge runtime, deploy business logic to the device from the cloud.
17
17
18
-
To learn more about how the IoT Edge runtime works and what components are included, see [Understand the Azure IoT Edge runtime and its architecture](iot-edge-runtime.md).
18
+
To learn more about how the IoT Edge runtime works and what components it includes, see [Understand the Azure IoT Edge runtime and its architecture](iot-edge-runtime.md).
19
19
20
20
## Deploy from Azure CLI
21
21
@@ -40,9 +40,9 @@ You can't deploy a remote Bicep file. Save a copy of the [Bicep file](https://ra
40
40
az account list --output table
41
41
```
42
42
43
-
1. Copy the SubscriptionID field for the subscription you'd like to use.
43
+
1. Copy the *SubscriptionID* field for the subscription you want to use.
44
44
45
-
1. Set your working subscription with the ID that you copied:
45
+
1. Set your working subscription with the ID you copied:
46
46
47
47
```azurecli
48
48
az account set -s <SubscriptionId>
@@ -69,7 +69,7 @@ You can't deploy a remote Bicep file. Save a copy of the [Bicep file](https://ra
To authenticate with an SSH key, you may do so by specifying an **authenticationType** of `sshPublicKey`, then provide the value of the SSH key in the **adminPasswordOrKey** parameter. For example:
72
+
To authenticate with an SSH key, specify an **authenticationType** of `sshPublicKey`, then provide the value of the SSH key in the `adminPasswordOrKey` parameter. For example:
73
73
74
74
```azurecli
75
75
#Generate the SSH Key
@@ -86,9 +86,9 @@ You can't deploy a remote Bicep file. Save a copy of the [Bicep file](https://ra
1.Verify that the deployment completed successfully. A virtual machine resource should be deployed into the selected resource group. Take note of the machine name, this should be in the format `vm-0000000000000`. Also, take note of the associated **DNS Name**, which should be in the format `<dnsLabelPrefix>`.`<location>`.cloudapp.azure.com.
89
+
1.Check that the deployment completed successfully. A virtual machine resource is deployed into the selected resource group. Note the machine name, which is in the format `vm-0000000000000`. Also, note the associated **DNS Name**, which is in the format `<dnsLabelPrefix>`.`<location>`.cloudapp.azure.com.
90
90
91
-
The **DNS Name**can be obtained from the JSON-formatted output of the previous step, within the **outputs** section as part of the **public SSH** entry. The value of this entry can be used to SSH into to the newly deployed machine.
91
+
You can get the **DNS Name** from the JSON-formatted output of the previous step, in the **outputs** section as part of the **public SSH** entry. Use this value to SSH into the newly deployed machine.
92
92
93
93
```bash
94
94
"outputs": {
@@ -99,9 +99,9 @@ You can't deploy a remote Bicep file. Save a copy of the [Bicep file](https://ra
99
99
}
100
100
```
101
101
102
-
The **DNS Name**can also be obtained from the **Overview** section of the newly deployed virtual machine within the Azure portal.
102
+
You can also get the **DNS Name** from the **Overview** section of the newly deployed virtual machine in the Azure portal.
103
103
104
-
:::image type="content" source="./media/how-to-install-iot-edge-ubuntuvm/iotedge-vm-dns-name.png" alt-text="Screenshot showing the DNS name of the I o T Edge virtual machine." lightbox="./media/how-to-install-iot-edge-ubuntuvm/iotedge-vm-dns-name.png":::
104
+
:::image type="content" source="./media/how-to-install-iot-edge-ubuntuvm/iotedge-vm-dns-name.png" alt-text="Screenshot showing the DNS name of the IoT Edge virtual machine." lightbox="./media/how-to-install-iot-edge-ubuntuvm/iotedge-vm-dns-name.png":::
105
105
106
106
1. If you want to SSH into this VM after setup, use the associated **DNS Name** with the command:
107
107
`ssh <adminUsername>@<DNS_Name>`
@@ -110,7 +110,7 @@ You can't deploy a remote Bicep file. Save a copy of the [Bicep file](https://ra
110
110
111
111
Now that you have an IoT Edge device provisioned with the runtime installed, you can [deploy IoT Edge modules](how-to-deploy-modules-portal.md).
112
112
113
-
If you are having problems with the IoT Edge runtime installing properly, check out the [troubleshooting](troubleshoot.md) page.
113
+
If you're having problems with the IoT Edge runtime installing properly, check out the [troubleshooting](troubleshoot.md) page.
114
114
115
115
To update an existing installation to the newest version of IoT Edge, see [Update the IoT Edge security daemon and runtime](how-to-update-iot-edge.md).
0 commit comments