Merge pull request #271519 from arunguru-msft/arunguru-removeiotmarketplace

Remove IOT marketplace references from SQL Edge documentation

Author: prmerger-automator[bot]

articles/azure-sql-edge/configure.md

@@ -60,7 +60,7 @@ Add values in **Container Create Options**.
 
 ## Configure by using an `mssql.conf` file
 
-Azure SQL Edge doesn't include the [mssql-conf configuration utility](/sql/linux/sql-server-linux-configure-mssql-conf/) like SQL Server on Linux does. You need to manually configure the mssql.conf file and place it in the persistent storage drive that is mapped to the /var/opt/mssql/ folder in the SQL Edge module. When you're deploying SQL Edge from Azure Marketplace, this mapping is specified as the **Mounts** option in the **Container Create Options**.
+Azure SQL Edge doesn't include the [mssql-conf configuration utility](/sql/linux/sql-server-linux-configure-mssql-conf/) like SQL Server on Linux does. You need to manually configure the mssql.conf file and place it in the persistent storage drive that is mapped to the /var/opt/mssql/ folder in the SQL Edge module. When you're deploying SQL Edge through Azure IoT Hub, this mapping is specified as the **Mounts** option in the **Container Create Options**.
 
 ```json
 {
@@ -126,7 +126,7 @@ traceflag2 = 1204
 
 ## Run Azure SQL Edge as non-root user
 
-By default, the Azure SQL Edge containers run with a non-root user/group. When deployed through the Azure Marketplace (or using `docker run`), unless a different user/group is specified, SQL Edge containers starts up as the mssql (non-root) user. To specify a different non-root user during deployment, add the `*"User": "<name|uid>[:<group|gid>]"*` key-value pair under container create options. In the following example, SQL Edge is configured to start as the user `*IoTAdmin*`.
+By default, the Azure SQL Edge containers run with a non-root user/group. When deployed through the Azure IoT Hub (or using `docker run`), unless a different user/group is specified, SQL Edge containers starts up as the mssql (non-root) user. To specify a different non-root user during deployment, add the `*"User": "<name|uid>[:<group|gid>]"*` key-value pair under container create options. In the following example, SQL Edge is configured to start as the user `*IoTAdmin*`.
 
 ```json
 {

articles/azure-sql-edge/deploy-portal.md

@@ -26,45 +26,26 @@ Azure SQL Edge is a relational database engine optimized for IoT and Azure IoT E
 > [!NOTE]  
 > To deploy an Azure Linux VM as an IoT Edge device, see this [quickstart guide](../iot-edge/quickstart-linux.md).
 
-## Deploy SQL Edge Module from Azure Marketplace
+## Deploy Azure SQL Edge Module using IoT Hub
 
-Azure Marketplace is an online applications and services marketplace where you can browse through a wide range of enterprise applications and solutions that are certified and optimized to run on Azure, including [IoT Edge modules](https://azuremarketplace.microsoft.com/marketplace/apps/category/internet-of-things?page=1&subcategories=iot-edge-modules). Azure SQL Edge can be deployed to an edge device through the marketplace.
+Azure SQL Edge can be deployed using instructions from [Deploy modules from Azure portal](/azure/iot-edge/how-to-deploy-modules-portal). The image URI for Azure SQL Edge is `mcr.microsoft.com/azure-sql-edge:latest`.
 
-1. Find the Azure SQL Edge module on the Azure Marketplace.
+1. On the **Add IoT Edge Module** page, specify the desired values for the *IoT Edge Module Name*, *Image URI*, *Restart Policy* and *Desired Status*.
 
-   :::image type="content" source="media/deploy-portal/find-offer-marketplace.png" alt-text="Screenshot of SQL Edge in the Azure Marketplace.":::
+   Use the following image URI depending on the edition you want to deploy:
+   - *Developer edition* - `mcr.microsoft.com/azure-sql-edge/developer`
+   - *Premium edition* - `mcr.microsoft.com/azure-sql-edge/premium`
 
-1. Pick the software plan that best matches your requirements and select **Create**.
-
-   :::image type="content" source="media/deploy-portal/pick-correct-plan.png" alt-text="Screenshot showing how to pick the correct software plan.":::
-
-1. On the Target Devices for IoT Edge Module page, specify the following details and then select **Create**.
-
-   | Field | Description |
-   | --- | --- |
-   | **Subscription** | The Azure subscription under which the IoT Hub was created |
-   | **IoT Hub** | Name of the IoT Hub where the IoT Edge device is registered and then select "Deploy to a device" option |
-   | **IoT Edge Device Name** | Name of the IoT Edge device where SQL Edge would be deployed |
-
-1. On the **Set Modules on device:** page, select the Azure SQL Edge module under **IoT Edge Modules**. The default module name is set to *AzureSQLEdge*.
-
-1. On the *Module Settings* section of the **Update IoT Edge Module** pane, specify the desired values for the *IoT Edge Module Name*, *Restart Policy* and *Desired Status*.
-
-   > [!IMPORTANT]  
-   > Don't change or update the **Image URI** settings on the module.
-
-1. On the *Environment Variables* section of the **Update IoT Edge Module** pane, specify the desired values for the environment variables. For a complete list of Azure SQL Edge environment variables, see [Configure using environment variables](configure.md#configure-by-using-environment-variables). The following default environment variables are defined for the module.
+1. On the *Environment Variables* section of the **Add IoT Edge Module** page, specify the desired values for the environment variables. For a complete list of Azure SQL Edge environment variables, see [Configure using environment variables](configure.md#configure-by-using-environment-variables).
 
    | Parameter | Description |
    | --- | --- |
-   | MSSQL_SA_PASSWORD | Change the default value to specify a strong password for the SQL Edge admin account. |
-   | MSSQL_LCID | Change the default value to set the desired language ID to use for SQL Edge. For example, 1036 is French. |
-   | MSSQL_COLLATION | Change the default value to set the default collation for SQL Edge. This setting overrides the default mapping of language ID (LCID) to collation. |
-
-   > [!IMPORTANT]  
-   > Don't change or update the `ACCEPT_EULA` environment variable for the module.
+   | ACCEPT_EULA | Set this value to `Y` to accept the [End-User Licensing Agreement](https://go.microsoft.com/fwlink/?linkid=2139274) |
+   | MSSQL_SA_PASSWORD | Set the value to specify a strong password for the SQL Edge admin account. |
+   | MSSQL_LCID | Set the value to set the desired language ID to use for SQL Edge. For example, 1036 is French. |
+   | MSSQL_COLLATION | Set the value to set the default collation for SQL Edge. This setting overrides the default mapping of language ID (LCID) to collation. |
 
-1. On the *Container Create Options* section of the **Update IoT Edge Module** pane, update the following options as per requirement.
+1. On the *Container Create Options* section of the **Add IoT Edge Module** page, set the options as per requirement.
 
    - **Host Port**
 
@@ -107,12 +88,16 @@ Azure Marketplace is an online applications and services marketplace where you c
    ```
 
    > [!IMPORTANT]  
-   > Don't change the `PlanId` environment variable defined in the create config setting. If this value is changed, the Azure SQL Edge container will fail to start.
+   > Set the `PlanId` environment variable based on the edition installed.
+   > - *Developer edition* - `asde-developer-on-iot-edge`
+   > - *Premium edition* - `asde-premium-on-iot-edge`
+   >
+   > If this value is set incorrectly, the Azure SQL Edge container fails to start.
 
    > [!WARNING]  
    > If you reinstall the module, remember to remove any existing bindings first, otherwise your environment variables will not be updated.
 
-1. On the **Update IoT Edge Module** pane, select **Update**.
+1. On the **Add IoT Edge Module** page, select **Add**.
 1. On the **Set modules on device** page, select **Next: Routes >** if you need to define routes for your deployment. Otherwise select **Review + Create**. For more information on configuring routes, see [Deploy modules and establish routes in IoT Edge](../iot-edge/module-composition.md).
 1. On the **Set modules on device** page, select **Create**.
 

articles/azure-sql-edge/overview.md

@@ -30,7 +30,7 @@ What is Azure SQL Edge video on Channel 9:
 
 Azure SQL Edge supports two deployment modes.
 
-- Connected deployment through Azure IoT Edge: Azure SQL Edge is available on the Azure Marketplace and can be deployed as a module for [Azure IoT Edge](../iot-edge/about-iot-edge.md). For more information, see [Deploy Azure SQL Edge](deploy-portal.md).<br>
+- Connected deployment through Azure IoT Edge: Azure SQL Edge is available as a module for [Azure IoT Edge](../iot-edge/about-iot-edge.md). For more information, see [Deploy Azure SQL Edge](deploy-portal.md).
 
 :::image type="content" source="media/overview/overview.png" alt-text="Diagram of SQL Edge overview.":::
 

articles/azure-sql-edge/troubleshoot.md

@@ -20,7 +20,7 @@ This article provides information about possible errors seen when deploying and
 
 Azure SQL Edge supports two deployment models:
 
-- Connected deployment through Azure IoT Edge: Azure SQL Edge is available on the Azure Marketplace and can be deployed as a module for [Azure IoT Edge](../iot-edge/about-iot-edge.md). For more information, see [Deploy Azure SQL Edge](deploy-portal.md).<br>
+- Connected deployment through Azure IoT Edge: Azure SQL Edge can be deployed as a module for [Azure IoT Edge](../iot-edge/about-iot-edge.md). For more information, see [Deploy Azure SQL Edge](deploy-portal.md).<br>
 
 - Disconnected deployment: Azure SQL Edge container images can be pulled from Docker hub and deployed either as a standalone container or on a Kubernetes cluster. For more information, see [Deploy Azure SQL Edge with Docker](disconnected-deployment.md) and [Deploy an Azure SQL Edge container in Kubernetes](deploy-kubernetes.md).
 

articles/azure-sql-edge/tutorial-set-up-iot-edge-modules.md

@@ -75,11 +75,9 @@ Now, specify the container credentials in the IoT Edge module.
 
 ## Deploy the Azure SQL Edge module
 
-1. Deploy the Azure SQL Edge module by selecting on **+ Add** and then **Marketplace Module**.
+1. Deploy the Azure SQL Edge module by selecting on **+ Add** and then **IoT Edge Module**.
 
-1. On the **IoT Edge Module Marketplace** pane, search for *Azure SQL Edge* and pick *Azure SQL Edge Developer*.
-
-1. Select the newly added *Azure SQL Edge* module under **IoT Edge Modules** to configure the Azure SQL Edge module. For more information on the configuration options, see [Deploy Azure SQL Edge](./deploy-portal.md).
+1. Set the configuration options in **Add IoT Edge Modules** page to deploy Azure SQL Edge module. For more information on the configuration options, see [Deploy Azure SQL Edge](./deploy-portal.md).
 
 1. Add the `MSSQL_PACKAGE` environment variable to the *Azure SQL Edge* module deployment, and specify the SAS URL of the database dacpac file created in step 8 of [Part one](tutorial-deploy-azure-resources.md) of this tutorial.