Merge branch 'sim-vendor-integration' into 2303-PR

Author: James-Green-Microsoft

articles/private-5g-core/collect-required-information-for-private-mobile-network.md

@@ -75,6 +75,7 @@ Note that once the SIM group is created, the encryption type cannot be changed.
 
    - Manually entering values for each SIM into fields in the Azure portal. This option is best when provisioning a few SIMs.
    - Importing a JSON file containing values for one or more SIM resources. This option is best when provisioning a large number of SIMs. The file format required for this JSON file is given in [JSON file format for provisioning SIMs](#json-file-format-for-provisioning-sims). You'll need to use this option if you're deploying your private mobile network with an ARM template.
+   - Importing an encrypted JSON file, provided by your SIM vendor, containing values for one or more SIM resources. You'll need to use this option if you're deploying your private mobile network with a JSON file provided by one of our SIM vendor partners. See [Collecting information for provisioning SIM vendor provided SIMs](#collecting-information-for-provisioning-sim-vendor-provided-sims) rather than collecting the values the next step.
 
 1. Collect each of the values given in the following table for each SIM resource you want to provision.
 
@@ -112,6 +113,58 @@ The following example shows the file format you'll need if you want to provision
 ]
 ```
 
+## Collecting information for provisioning SIM vendor provided SIMs
+
+Collect and edit each of the values in the following table for each SIM resource you want to provision using an encrypted JSON file, provided by your SIM vendor.
+
+|Value  | JSON file parameter name |
+|---------|---------|
+|The name for the SIM resource. The name must only contain alphanumeric characters, dashes, and underscores.|`name`|
+|The type of device that is using this SIM. This value is an optional, free-form string. You can use it as required to easily identify device types that are using the enterprise's mobile networks.|`deviceType`|
+|The SIM policy ID to apply to the SIM. See [Decide whether you want to use the default service and SIM policy](#decide-whether-you-want-to-use-the-default-service-and-sim-policy).|`simPolicy`|
+|The static IP configuration values for the SIM: **attachedDataNetwork**, **slice**, and **staticIp**.|`staticIpConfigurations`|
+
+### Encrypted JSON file format for provisioning vendor provided SIMs
+
+The following example shows the file format to provision your SIM resources using a SIM vendor provided encrypted JSON file.
+
+```json
+{  
+  "version": 1,  
+  "azureKey": 1,  
+  "vendorKeyFingerprint": "A5719BCEFD6A2021A11D7649942ECC14", 
+  "encryptedTransportKey": "0EBAE5E2D31A1BE48495F6DCA65983EEAE6BA6B75A92040562EAD84079BF701CBD3BB1602DB74E85921184820B78A02EC709951195DC87E44481FDB6B826DF775E29B7073644EA66649A14B6CA6B0EE75DE8B4A8D0D5186319E37FBF165A691E607CFF8B65F3E5E9D448049704DE4EA047101ADA4554A543F405B447B8DB687C0B7624E62515445F3E887B3328AA555540D9959752C985490586EF06681501A89594E28F98BF66F179FE3F1D2EE13C69BC42C30A8D3DC6898B8160FC66CDDEE164760F27B68A07BA4C4AE5AFFEA45EE8342E1CA8470150ED6AF4215CEF173418E60E2B1DF4A8C2AE6F0C9A291F5D185ECAD0D94D48EFD06570A0C1AE27D5EC20",  
+  "signedTransportKey": "83515CC47C8890F62D4A0D16DE58C2F2DCFD827C317047693A46B9CA1F9EBC33CCDB8CABE04A275D65E180813CCFF43FC2DA95E19E2B9FF2588AE0914418DC9CB5506EB7AEADB272F5DAB9F0B1CCFAD62B95C91D4F4680A350F56D2A7F8EC863F4D61E1D7A38746AEE6C6391D619CCFCFA2B6D554671D91A26484CD6E120D84917FBF69D3B56B2AA8F2B36AF88492F1A7E267594B6C1596B81A81079540EC3F31869294BFEB225DFB171DE557B8C05D7C963E047E3AF36D1387FEDA28E55E411E5FB6AED178FB9C92D674D71AF8FEB6462F509E6423D4EBE0EC84E4135AA6C7A36F849A14A6A70E7188E08278D515BD95A549645E9D595D1DEC13E1A68B9CB67",  
+  "sims": [  
+    {  
+      "name": "SIM 1",  
+      "properties": {  
+        "deviceType": "Sensor",  
+       "integratedCircuitCardIdentifier": "8922345678901234567",  
+        "internationalMobileSubscriberIdentity": "001019990010002",  
+        "encryptedCredentials": "3ED205BE2DD7F0E467283EC55F9E8F3588B68DC98811BE671070C65EFDE0CCCAD18C8B663231C80FB478F753A6B09142D06982421261679B7BB112D36473EA7EF973DCF7F634124B58DD945FE61D4B16978438CB33E64D3AA58B5C38A0D97030B5F95B16E308D919EB932ACCD36CB8C2838C497B3B38A60E3DD385",  
+        "simPolicy": {  
+          "id": "/subscriptions/subid/resourceGroups/rg1/providers/Microsoft.MobileNetwork/mobileNetworks/testMobileNetwork/simPolicies/MySimPolicy"  
+        },  
+        "staticIpConfiguration": [
+                {
+                    "attachedDataNetwork": {
+                        "id": "/subscriptions/subid/resourceGroups/rg1/providers/Microsoft.MobileNetwork/packetCoreControlPlanes/TestPacketCoreCP/packetCoreDataPlanes/TestPacketCoreDP/attachedDataNetworks/TestAttachedDataNetwork"
+                    },
+                    "slice": {
+                        "id": "/subscriptions/subid/resourceGroups/rg1/providers/Microsoft.MobileNetwork/mobileNetworks/testMobileNetwork/slices/testSlice"
+                    },
+                    "staticIp": {
+                        "ipv4Address": "2.4.0.1"
+                    } 
+          }  
+        ]  
+      }  
+    }  
+  ]  
+}  
+```
+
 ## Decide whether you want to use the default service and SIM policy
 
  Azure Private 5G Core offers a default service and SIM policy that allow all traffic in both directions for all the SIMs you provision. They're designed to allow you to quickly deploy a private mobile network and bring SIMs into service automatically, without the need to design your own policy control configuration.

articles/private-5g-core/how-to-guide-deploy-a-private-mobile-network-azure-portal.md

@@ -20,7 +20,7 @@ Private mobile networks provide high performance, low latency, and secure connec
 - Ensure you can sign in to the Azure portal using an account with access to the active subscription you identified in [Complete the prerequisite tasks for deploying a private mobile network](complete-private-mobile-network-prerequisites.md). This account must have the built-in Contributor or Owner role at the subscription scope.
 - Collect all of the information listed in [Collect the required information to deploy a private mobile network](collect-required-information-for-private-mobile-network.md). You may also need to take the following steps based on the decisions you made when collecting this information.
 
-  - If you decided you wanted to provision SIMs using a JSON file, ensure you've prepared this file and made it available on the machine you'll use to access the Azure portal. For more information on the file format, see [JSON file format for provisioning SIMs](collect-required-information-for-private-mobile-network.md#json-file-format-for-provisioning-sims).
+  - If you decided you want to provision SIMs using a JSON file, ensure you've prepared this file and made it available on the machine you'll use to access the Azure portal. For more information on the file format, see [JSON file format for provisioning SIMs](collect-required-information-for-private-mobile-network.md#json-file-format-for-provisioning-sims) or [Encrypted JSON file format for provisioning vendor provided SIMs](collect-required-information-for-private-mobile-network.md#encrypted-json-file-format-for-provisioning-vendor-provided-sims).
   - If you decided you want to use the default service and SIM policy, identify the name of the data network to which you want to assign the policy.
 
 ## Deploy your private mobile network
@@ -51,6 +51,10 @@ In this step, you'll create the Mobile Network resource representing your privat
 
     :::image type="content" source="media/how-to-guide-deploy-a-private-mobile-network-azure-portal/create-private-mobile-network-sims-tab.png" alt-text="Screenshot of the Azure portal showing the SIMs configuration tab.":::
 
+    - If you select **Upload Encrypted JSON file**, the following notice will appear.
+
+    :::image type="content" source="media/how-to-guide-deploy-a-private-mobile-network-azure-portal/create-private-mobile-network-vendor-sims-notice.png" alt-text="Screenshot of the Azure portal showing the a notice on the SIMs configuration tab stating: At the moment, you will not be able to upload the encrypted SIMs under this SIM group. However, you will be able upload the encrypted SIMs under the SIM group section, once the above named SIM group gets created.":::
+
 1. If you're provisioning SIMs at this point, you'll need to take the following additional steps.
    1. If you want to use the default service and SIM policy, set **Do you wish to create a basic, default SIM policy and assign it to these SIMs?** to **Yes**, and then enter the name of the data network into the **Data network name** field that appears. 
    1. Under **Enter SIM group information**, set **SIM group name** to your chosen name for the SIM group to which your SIMs will be added.