add new concept articles

Author: meaghanlewis

articles/modeling-simulation-workbench/disaster-recovery.md

@@ -0,0 +1,74 @@
+---
+title: Disaster recovery for Modeling and Simulation Workbench
+description: This article provides an overview of disaster recovery for Azure Modeling and Simulation Workbench workbench component.
+author: meaghanlewis
+ms.author: mosagie
+ms.service: modeling-simulation-workbench
+ms.topic: conceptual
+ms.date: 08/21/2024
+---
+
+# Disaster recovery for Modeling and Simulation Workbench
+
+This article explains how to configure a disaster recovery environment for Azure Modeling and Simulation Workbench. Azure data center outages are rare but can last anywhere from a few minutes to hours. Data Center outages can cause disruption to the environments hosted in that data center. By following the steps detailed in this article, Azure Modeling and Simulation workbench customers can continue to operate in the cloud in the event of a data center outage for the primary region hosting your workbench instance.
+
+Planning for disaster recovery involves identifying expected recovery point objectives (RPO) and recovery time objectives (RTO) for your instance. Based upon your risk-tolerance and expected RPO, follow these instructions at an interval appropriate for your business needs.
+
+A typical disaster recovery workflow starts with a failure of a critical service in your primary region. As the issue gets investigated, Azure will publish an expected time for the primary region to recover. If this timeframe is not acceptable for business continuity, and the problem does not impact your secondary region, you would start the process to fail over to the secondary region.
+
+## Achieving business continuity for Azure Modeling and Simulation Workbench
+To be prepared for a data center outage, you can have a Modeling and Simulation workbench instance provisioned in a secondary region. 
+
+These Workbench resources can be configured to match the resources which exist in the primary Azure Modeling and Simulation workbench instance. Users in the workbench instance environment can be provisioned ahead of time, or when you switch to the secondary region. Chamber and connector resources can be put in a stopped state post deployment to invoke idle billing meters when not being used actively. 
+
+Alternatively, if you do not want to have an Azure Modeling and Simulation Workbench instance provisioned in the secondary region until an outage impacts your primary region, you can follow the provided procedures in the Quickstart but stop before actually creating the Azure Modeling and Simulation Workbench instance in the secondary region. That step can be executed when you choose to create the workbench resources in the secondary region as a fail over.
+
+## Prerequisites
+
+- Ensure that the services and features that your account uses are supported in the target secondary region.
+
+## Verify Entra ID tenant
+
+The workspace source and destination can be in the same subscription. If source and destination for workbench will be different subscriptions, the subscriptions must exist within the same Entra ID tenant. Use Azure PowerShell to verify that both subscriptions have the same tenant ID.
+
+```powershell
+Get-AzSubscription -SubscriptionId <your-source-subscription>.TenantId
+
+Get-AzSubscription-SubscriptionId <your-destination-subscription>.TenantId
+```
+
+## Prepare
+
+To be prepared to work in a backup region, you would need to do some preparation ahead of the outage.
+
+First identify your backup region.
+
+List of supported regions can be found on the [Azure product availability roadmap](https://global.azure.com/product-roadmap/pam/roadmap), and searching for the service name: **Azure Modeling and Simulation Workbench**.
+  
+Then, create a backup of your Azure Key Vault and keys used by Azure Modeling and Simulation in Key Vault including:
+
+1.	Application Client Id key
+2.	Application Secret key
+
+## Configure the new instance
+
+In the event of your primary region failure, and decision to work in a backup region, you would create a Modeling and Simulation Workbench instance in your backup region.
+
+1. Register to the Azure Modeling and Simulation Workbench Resource Provider as described in [Create an Azure Modeling and Simulation Workbench](/azure/modeling-simulation-workbench/quickstart-create-portal#register-azure-modeling-and-simulation-workbench-resource-provider). 
+
+1. Create an Azure Modeling and Simulation Workbench using this section of the Quickstart.
+
+1. If desired, upload data into the new backup instance following Upload Files section of instructions.
+
+You can now do your work in the new workbench instance created in the backup region.
+
+
+## Cleanup
+
+Once your primary region is back up and operating, and you no longer need your backup instance, you can delete it.
+
+## Related information
+
+- [Backup and disaster recovery for Azure applications](/azure/reliability/cross-region-replication-azure)
+
+- [Azure status](https://azure.status.microsoft/status)

articles/modeling-simulation-workbench/shared-storage.md

@@ -0,0 +1,23 @@
+---
+title: Shared storage for Modeling and Simulation Workbench
+description: This article provides an overview of disaster recovery for Azure Modeling and Simulation Workbench workbench component.
+author: meaghanlewis
+ms.author: mosagie
+ms.service: modeling-simulation-workbench
+ms.topic: conceptual
+ms.date: 08/21/2024
+---
+
+# Shared storage for Modeling and Simulation Workbench
+
+To enable cross team and/or cross-organization collaboration in a secure manner within the workbench, a shared storage resource allows for selective data sharing between collaborating parties. It is an Azure NetApp Files based storage volume and is available to deploy in multiples of 4TB’s. Workbench owners can create multiple shared storage instances on demand and dynamically link them to existing chambers to facilitate secure collaboration. 
+
+Users who are provisioned to a specific chamber can access all shared storage volumes linked to that chamber. Once users get de-provisioned from a chamber or that chamber gets deleted, they lose access to any linked shared storage volumes.  
+
+## Key features of shared storage
+
+**Performance**: A Shared storage resource within the workbench is high-performance Azure NetApp Files based, targeting complex engineering workloads. It can be used to run simulations and is not limited to being used as a data transfer mechanism.  
+
+**Scalability**: Users can adjust the storage capacity and performance tier according to their needs, just like chamber private storage.  
+
+**Management**: Workbench Owners can manage storage capacity, resize storage, and change performance tiers through the Azure portal.  

articles/modeling-simulation-workbench/toc.yml

@@ -28,7 +28,13 @@ items:
     - name: Data pipeline
       href: ./concept-data-pipeline.md
     - name: License service
-      href: ./concept-license-service.md      
+      href: ./concept-license-service.md
+    - name: Shared storage
+      href: ./shared-storage.md
+    - name: Business Continuity
+      items:
+        - name: Disaster Recovery
+          href: ./disaster-recovery.md      
 - name: How-to guides
   items: 
     - name: Manage users