Merge pull request #285392 from yousefi-msft/release-mswb

MSWB release candidate

Author: v-ccolin

.openpublishing.redirection.json

@@ -10,7 +10,7 @@
       "redirect_url": "/previous-versions/azure/azure-app-configuration/rest-api-fiddler",
       "redirect_document_id": false
     },
-    { 
+    {
       "source_path": "articles/kinect-dk/index.yml",
       "redirect_url": "/previous-versions/azure/kinect-dk/index",
       "redirect_document_id": false
@@ -4754,6 +4754,11 @@
       "source_path_from_root": "/articles/virtual-network/virtual-network-service-endpoint-policies-powershell.md",
       "redirect_url": "/azure/virtual-network/virtual-network-service-endpoint-policies",
       "redirect_document_id": false
+    },
+    {
+      "source_path_from_root": "/articles/modeling-simulation-workbench/how-to-guide-manage-storage.md",
+      "redirect_url": "/azure/modeling-simulation-workbench/concept-storage",
+      "redirect_document_id": false
     }
   ]
-}
+}

articles/modeling-simulation-workbench/concept-chamber.md

@@ -9,35 +9,37 @@ ms.topic: conceptual
 ms.date: 01/01/2023
 # Customer intent: As a Modeling and Simulation Workbench user, I want to understand the chamber component.
 ---
+# Chambers in the Azure Modeling and Simulation Workbench
 
-# Chamber: Azure Modeling and Simulation Workbench
+In the Azure Modeling and Simulation Workbench, chambers are a security boundary for a group virtual machines (VM) (nodes) and share common users. A chamber provides a full-featured and secure environment for users to run engineering applications and workloads together in isolation. Chamber VMs are all on the same subnet and have no internet access.
 
-In Azure Modeling and Simulation Workbench, a chamber is defined as a group of connected computers (nodes) that work together as a single system.  A chamber provides a full-featured and secure environment for users to run engineering applications and workloads together.
+## Key features
 
-- Chambers offer optimized infrastructure, allowing users to choose from varied VM sizes, storage options, and compute resources to constitute workloads.
-- Chambers enable a preconfig environment for license server access and full-featured workload tools.
-- On-demand chambers are nested to Modeling and Simulation [Workbench](./concept-workbench.md) resource.
+* Chambers offer optimized infrastructure, allowing users to choose from varied VM sizes, storage options, and compute resources to constitute workloads.
+* Chambers enable a preconfigured, isolated environment for license server access and full-featured workload tools.
+* Chambers are encapsulated in the [Workbench](./concept-workbench.md) resource.
 
 ## Chamber environment
 
 Chambers create a secure and isolated environment by adding private IP access and removing internet access. Public domain access is restricted to authorized networks over encrypted sessions enabled by the connector component. A [connector](./concept-connector.md)  exists per chamber that supports the protocols established through VPN, Azure Express Route, or allowlisted Public IP addresses.
 
-Only provisioned users can access the chamber environment. User provisioning is done at the chamber component using IAM [(Access Control)](/azure/role-based-access-control/role-assignments-portal).  This enables Cross team and/or cross-organization individuals to collaborate on the same projects through the chambers. Multifactor authentication (MFA) enabled through Microsoft Entra ID is recommended to enhance your organization's security.
+Only provisioned users can access the chamber environment. User provisioning is done at the chamber level using Azure's [Identity Access Management](/azure/role-based-access-control/role-assignments-portal). This enables cross-team and/or cross-organization collaboration on the same projects through chambers. Multifactor authentication (MFA) enabled through Microsoft Entra ID is recommended to enhance your organization's security.
 
 ## Chamber storage
 
-Users can resize and tailor the chambers to support storage requirement needs throughout the design process. Chamber users can also allocate Chamber VMs on demand, select the right-sized VM/CPU for the task/job at hand, and decommission the workload when the job is done to save costs.
+Users can resize and tailor the chambers to support storage requirement needs throughout the design process. Chamber users can also allocate chamber VMs on demand, select the right-sized VM/CPU for the task/job at hand, and decommission the workload when the job is done to save costs.
 
-### Right-sizing
+### Cost optimization
 
-The right-sizing feature reduces the Azure spend by identifying idle and underutilized resources. For example:
+Administrators can optimize their resource consumption without necessarily destroying resources or moving data by:
 
-- By managing the size and number of virtual machines.
-- By stopping unused workloads, connectors and chambers.
-- By managing the size and performance tier of chamber storages.
+* [Managing](./how-to-guide-chamber-vm.md) the size and number of virtual machines.
+* [Idling](./how-to-guide-chamber-idle.md) unused chambers to reduce cost without deleting VMs or storage.
+* [Managing](./how-to-guide-manage-chamber-storage.md) the size and performance tier of chamber storages.
 
 Learn more about reducing service costs using [Azure Advisor](/azure/advisor/advisor-cost-recommendations#optimize-spend-for-mariadb-mysql-and-postgresql-servers-by-right-sizing) and [right-size VMs best practices](/azure/cloud-adoption-framework/migrate/azure-best-practices/migrate-best-practices-costs#best-practice-right-size-vms).
 
-## Related content
+## Next steps
 
-- [Connector](./concept-connector.md)
+> [!div class="nextstepaction"]
+> [Create a chamber VM](./how-to-guide-chamber.md)

articles/modeling-simulation-workbench/concept-connector.md

@@ -1,27 +1,36 @@
 ---
-title: "Connector: Azure Modeling and Simulation Workbench"
-description: Overview of how the Azure Modeling and Simulation Workbench implements connectors.
+title: "Connectors: Azure Modeling and Simulation Workbench"
+description: Connector implementation in Azure Modeling and Simulation Workbench.
 author: lynnar
 ms.author: lynnar
 ms.reviewer: yochu
 ms.service: modeling-simulation-workbench
 ms.topic: conceptual
 ms.date: 01/01/2023
-#Customer intent: As a Modeling and Simulation Workbench user, I want to understand the connector component.
+
+#Customer intent: As a Modeling and Simulation Workbench user, I want to understand the component.
 ---
+# Connectors in Azure Modeling and Simulation Workbench
+
+Connectors define the network access method between users and the Azure Modeling and Simulation Workbench chamber. Connectors support connectivity through allowlisted public IPs, VPN, or Azure ExpressRoute. A chamber can have only one connector configured at a time. Connectors also configure copy-paste functionality into chamber VMs. Connector types are immutable and once created can't be changed to another access model. Connectors are part of the Idle mode setting to reduce cost.
+
+## Public IP access via allowlist
+
+The Workbench can be built to allow users to connect directly from the internet, allowing flexible, open access. When a Public IP Connection is built, connections are permitted using an allowlist. The allowlist uses CIDR (Classless Interdomain Routing) notation to conveniently manage access from large network ranges, such as conference centers or corporate exit nodes. Only IPs listed in the allowlist are able to make connections to its associated chamber.
 
-# Connector: Azure Modeling and Simulation Workbench
+## Private Azure networking
 
-Connectors are used to define and configure the network access between an organization's on-premises or cloud environment into the Azure Modeling and Simulation Workbench chamber. The connector supports protocols established through VPN, Azure Express Route, or network Access Control Lists.
+A connector can be created for private network access from Azure virtual networks. This method is best suited where a private or controlled connection is required. Azure ExpressRoutes provide a dedicated connection from an on-premises infrastructure to an Azure data center and can be peered to the Workbench. With a VPN gateway, the Workbench can use a private network with extra encryption layers.
 
-## VPN or Azure Express Route
+### VPN
 
-For organizations who have an Azure network setup to manage access for their employees, they can have strict controls of the virtual network subnet addresses used for connecting into the chamber. At creation time of the connector, the Chamber Admin or Workbench Owner can connect a virtual network subnet with VPN gateway or ExpressRoute gateway to establish a secure connection from your on-premises network to the chamber. The subnet selection should be a non gateway subnet within the same virtual network with the gateway subnet for VPN gateway or ExpressRoute gateway.
+A VPN connector can be created which deploys infrastructure specifically for VPN access. The VPN connector is required if the chamber is accessed through a point-to-site or site-to-site VPN.
 
-## Allowlisted Public IP addresses
+### Azure ExpressRoute
 
-For those organizations who don't have an Azure network setup, or prefer to use the public network, they can configure their connector to allow access to the chamber via allowlisted Public IP addresses. The connector object allows the allowed IP list to be configured at creation time or added or removed dynamically after the connector object is created.
+[Azure ExpressRoute](/azure/expressroute/expressroute-introduction) provides secure, dedicated, encrypted connectivity from on-premises to an Azure landing zone. A Workbench Owner must create a connector expressly for ExpressRoute, providing the necessary virtual network, supporting network infrastructure, and peer the appropriate vnets.
 
-## Related content
+## Next step
 
-- [Data pipeline](./concept-data-pipeline.md)
+> [!div class="nextstepaction"]
+> [Create a connector](./how-to-guide-set-up-networking.md)

articles/modeling-simulation-workbench/concept-data-pipeline.md

@@ -18,23 +18,23 @@ The data pipeline enables users to bring data into the [chamber](./concept-chamb
 
 ## Importing data overview
 
-Users with access to the chamber can bring data into the chamber via AzCopy and an expiring SAS URI token they get from the chamber component.  They then use AzCopy to move data into the data pipeline endpoint. The chamber recognizes the data pipeline request and moves the file into the chamber.  For traceability purposes, when a file is moved into the chamber, the data pipeline automatically creates a file object in the chamber that represents the file data.
+Users with access to the chamber can bring data into the chamber via AzCopy and an expiring SAS URI token they get from the chamber component. They then use AzCopy to move data into the data pipeline endpoint. The chamber recognizes the data pipeline request and moves the file into the chamber. For traceability purposes, when a file is moved into the chamber, the data pipeline automatically creates a file object in the chamber that represents the file data.
 
 ## Exporting data overview
 
 Users with access to the chamber can export data from the chamber via the data pipeline.
 
-1. **Identify file to export.** The export process is triggered when a user places a file to export into a designated area within the chamber.  A Chamber Admin or Chamber User copies the file to the data out folder within the pipeline. The data pipeline detects the copied file and creates a file object. The file creation activity is traceable in the logs and enables the next step of the data pipeline.
+1. **Identify file to export.** The export process is triggered when a user places a file to export into a designated area within the chamber. A chamber Admin or chamber User copies the file to the data out folder within the pipeline. The data pipeline detects the copied file and creates a file object. The file creation activity is traceable in the logs and enables the next step of the data pipeline.
 
-1. **Request file to export.** A Chamber Admin reviews files in the data pipeline and requests to export files in the data out folder in the chamber. The pipeline creates a file request object. The export request activity is traceable in the logs and enables the next step of the data pipeline.
+1. **Request file to export.** A Chamber Admin reviews the files staged in the data pipeline and requests to export. The pipeline manager creates a file request object. The export request activity is traceable in the logs and enables the next step of the data pipeline.
 
-1. **Approve/reject export request.** The Workbench Owner approves or rejects the file request object for export. The export approval step must be completed by the Workbench Owner and can't be the same person who requested to export the data.
+1. **Approve/reject export request.** The Workbench Owner either approves or rejects the export file request. Only a Workbench Owner can approve or reject requests. The individual who approves or denies can't be the same person who initially requested the export.
 
-1. **Download file to export.** If a file is approved for export, the user gets a download URI from the file request object and copies it out of the chamber using AzCopy. The URI has an expiration timestamp and must be downloaded before it expires. If the URI expires, you need to request a new download URI.
+1. **Download file.** If a file is approved for export, the user gets a download URI from the file request object and copies it out of the chamber using AzCopy. The URI has an expiration timestamp and must be downloaded before it expires. If the URI expires, you need to request a new download URI.
 
-  > [!NOTE]
-  > Larger files take longer to be available to download after being approved and to download using AzCopy.  Check the expiration on the download URI and request a new one if the window has expired.
+ > [!NOTE]
+ > Larger files take longer to be available to download after being approved and to download using AzCopy. Check the expiration on the download URI and request a new one if the window has expired.
 
-## Related content
+## Next steps
 
-- [License service](./concept-license-service.md)
+- [License service](./concept-license-service.md)

articles/modeling-simulation-workbench/concept-license-service.md

@@ -12,24 +12,22 @@ ms.date: 01/01/2023
 
 # License service: Azure Modeling and Simulation Workbench
 
-A license service automates the installation of a license manager to help customers accelerate their engineering design.  A license service is integrated into Azure Modeling and Simulation Workbench.
+A license service automates the installation of a license manager to help customers accelerate their engineering design. A license service is integrated into Azure Modeling and Simulation Workbench.
 
 ## Overview
 
 Engineering design tools are widely used across industries to enable design teams to run their flows efficiently. Many of these proprietary software programs require licenses. License management is integrated into our flows via the most commonly used license manager, FLEXlm.
 
 Here's how the license service works:
 
-- For each deployed chamber within the workbench, we set up a license server and expose the FLEXlm HostID's to procure licenses.
-- Users request tool licenses for the specific HostID.
-- Once the license file is received from the tool vendor, users import it to enable the license service.
+For each deployed chamber within the workbench, we set up a license server and expose the FLEXlm HostID's to procure licenses. Users then request tool licenses referencing the specific HostID. Once the license file is received from the tool vendor, users import it to the chamber license server to enable the license service.
 
 ## Additional information
 
-For silicon EDA, our service automation deploys license servers for each of the four common software vendors (Synopsys, Cadence, Siemens, and Ansys) as part of resource creation to enable multi-vendor flows. The workbench also supports license service beyond these common EDA tool vendors with some manual configuration.
+For semiconductor Electronic Design Automation (EDA), our service automation deploys license servers for each of the four common software vendors (Synopsys, Cadence, Siemens, and Ansys) as part of resource creation to enable multi-vendor flows. The workbench also supports license service beyond these common EDA tool vendors with some manual configuration.
 
-This flow is extendible and can also include other software vendors across industry verticals."
+This flow is extendible and can also include other software vendors across industry verticals.
 
 ## Related content
 
-- Learn more about the benefits and key features of using [Shared storage](./shared-storage.md).
+- Learn more about the benefits and key features of using [shared storage](./shared-storage.md).