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
Copy file name to clipboardExpand all lines: articles/azure-government/compliance/azure-services-in-fedramp-auditscope.md
+8-10Lines changed: 8 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ ms.topic: article
7
7
ms.service: azure-government
8
8
ms.custom: references_regions
9
9
recommendations: false
10
-
ms.date: 11/09/2023
10
+
ms.date: 02/05/2023
11
11
---
12
12
13
13
# Azure, Dynamics 365, Microsoft 365, and Power Platform services compliance scope
@@ -50,7 +50,7 @@ For current Azure Government regions and available services, see [Products avail
50
50
This article provides a detailed list of Azure, Dynamics 365, Microsoft 365, and Power Platform cloud services in scope for FedRAMP High, DoD IL2, DoD IL4, DoD IL5, and DoD IL6 authorizations across Azure, Azure Government, and Azure Government Secret cloud environments. For other authorization details in Azure Government Secret and Azure Government Top Secret, contact your Microsoft account representative.
51
51
52
52
## Azure public services by audit scope
53
-
*Last updated: November 2023*
53
+
*Last updated: January 2024*
54
54
55
55
### Terminology used
56
56
@@ -88,6 +88,7 @@ This article provides a detailed list of Azure, Dynamics 365, Microsoft 365, and
88
88
|[Azure for Education](https://azureforeducation.microsoft.com/)|✅|✅|
89
89
|[Azure Information Protection](/azure/information-protection/)|✅|✅|
90
90
|[Azure Kubernetes Service (AKS)](../../aks/index.yml)|✅|✅|
|[Omnichannel for Customer Service (Formerly Dynamics 365 Chat and Omnichannel Engagement Hub)](/dynamics365/omnichannel/introduction-omnichannel)|✅|✅|
|[Storage: Blobs](../../storage/blobs/index.yml) (incl. [Azure Data Lake Storage Gen2](../../storage/blobs/data-lake-storage-introduction.md)) |✅|✅|
@@ -312,7 +311,7 @@ This article provides a detailed list of Azure, Dynamics 365, Microsoft 365, and
Copy file name to clipboardExpand all lines: articles/batch/batch-account-create-portal.md
+13-3Lines changed: 13 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -120,13 +120,13 @@ For detailed steps, see [Assign Azure roles by using the Azure portal](../role-b
120
120
121
121
### Create a key vault
122
122
123
-
User subscription mode requires [Azure Key Vault](/azure/key-vault/general/overview). The key vault must be in the same subscription and region as the Batch account and use a [Vault Access Policy](/azure/key-vault/general/assign-access-policy).
123
+
User subscription mode requires [Azure Key Vault](/azure/key-vault/general/overview). The key vault must be in the same subscription and region as the Batch account.
124
124
125
125
To create a new key vault:
126
126
127
127
1. Search for and select **key vaults** from the Azure Search box, and then select **Create** on the **Key vaults** page.
128
128
1. On the **Create a key vault** page, enter a name for the key vault, and choose an existing resource group or create a new one in the same region as your Batch account.
129
-
1. On the **Access configuration** tab, select **Vault access policy** under **Permission model**.
129
+
1. On the **Access configuration** tab, select either **Azure role-based access control** or **Vault access policy** under **Permission model**, and under **Resource access**, check all 3 checkboxes for **Azure Virtual Machine for deployment**, **Azure Resource Manager for template deployment** and **Azure Disk Encryption for volume encryption**.
130
130
1. Leave the remaining settings at default values, select **Review + create**, and then select **Create**.
131
131
132
132
### Create a Batch account in user subscription mode
@@ -140,8 +140,18 @@ To create a Batch account in user subscription mode:
140
140
141
141
### Grant access to the key vault manually
142
142
143
-
You can also grant access to the key vault manually.
143
+
You can also grant access to the key vault manually in [Azure portal](https://portal.azure.com).
144
144
145
+
#### If the Key Vault permission model is **Azure role-based access control**:
146
+
1. Select **Access control (IAM)** from the left navigation of the key vault page.
147
+
1. At the top of the **Access control (IAM)** page, select **Add** > **Add role assignment**.
148
+
1. On the **Add role assignment** screen, under **Role** tab, under **Job function roles** sub tab, select either **Key Vault Secrets Officer** or **Key Vault Administrator** role for the Batch account, and then select **Next**.
149
+
1. On the **Members** tab, select **Select members**. On the **Select members** screen, search for and select **Microsoft Azure Batch**, and then select **Select**.
150
+
1. Click the **Review + create** button on the bottom to go to **Review + assign** tab, and click the **Review + create** button on the bottom again.
151
+
152
+
For detailed steps, see [Assign Azure roles by using the Azure portal](../role-based-access-control/role-assignments-portal.md).
153
+
154
+
#### If the Key Vault permission model is **Vault access policy**:
145
155
1. Select **Access policies** from the left navigation of the key vault page.
146
156
1. On the **Access policies** page, select **Create**.
147
157
1. On the **Create an access policy** screen, select a minimum of **Get**, **List**, **Set**, and **Delete** permissions under **Secret permissions**. For [key vaults with soft-delete enabled](/azure/key-vault/general/soft-delete-overview), also select **Recover**.
Copy file name to clipboardExpand all lines: articles/certification/how-to-test-pnp.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,19 +26,19 @@ This article shows you how to:
26
26
The application code that runs on your IoT Plug and Play must:
27
27
28
28
- Connect to Azure IoT Hub using the [Device Provisioning Service (DPS)](../iot-dps/about-iot-dps.md).
29
-
- Follow the [IoT Plug an Play conventions](../iot-develop/concepts-developer-guide-device.md) to implement of telemetry, properties, and commands.
29
+
- Follow the [IoT Plug an Play conventions](../iot/concepts-developer-guide-device.md) to implement of telemetry, properties, and commands.
30
30
31
31
The application is software that's installed separately from the operating system or is bundled with the operating system in a firmware image that's flashed to the device.
32
32
33
-
Prior to certifying your device through the certification process for IoT Plug and Play, you will want to validate that the device implementation matches the telemetry, properties and commands defined in the [Digital Twins Definition Language (DTDL)](https://github.com/Azure/opendigitaltwins-dtdl) device model locally prior to submitting to the [Azure IoT Public Model Repository](../iot-develop/concepts-model-repository.md).
33
+
Prior to certifying your device through the certification process for IoT Plug and Play, you will want to validate that the device implementation matches the telemetry, properties and commands defined in the [Digital Twins Definition Language (DTDL)](https://github.com/Azure/opendigitaltwins-dtdl) device model locally prior to submitting to the [Azure IoT Public Model Repository](../iot/concepts-model-repository.md).
34
34
35
35
To meet the certification requirements, your device must:
36
36
37
37
- Connects to Azure IoT Hub using the [DPS](../iot-dps/about-iot-dps.md).
38
38
- Implement of telemetry, properties, or commands following the IoT Plug and Play convention.
39
39
- Describe the device interactions with a [DTDL v2](https://aka.ms/dtdl) model.
40
-
- Send the model ID during [DPS registration](../iot-develop/concepts-developer-guide-device.md#dps-payload) in the DPS provisioning payload.
41
-
- Announce the model ID during the [MQTT connection](../iot-develop/concepts-developer-guide-device.md#model-id-announcement).
40
+
- Send the model ID during [DPS registration](../iot/concepts-developer-guide-device.md#dps-payload) in the DPS provisioning payload.
41
+
- Announce the model ID during the [MQTT connection](../iot/concepts-developer-guide-device.md#model-id-announcement).
Copy file name to clipboardExpand all lines: articles/certification/how-to-troubleshoot-pnp.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -37,7 +37,7 @@ While running the tests, if you receive a result of `Passed with warnings`, this
37
37
38
38
## When you need help with the model repository
39
39
40
-
For IoT Plug and Play issues related to the model repository, refer to [our Docs guidance about the device model repository](../iot-develop/concepts-model-repository.md).
40
+
For IoT Plug and Play issues related to the model repository, refer to [our Docs guidance about the device model repository](../iot/concepts-model-repository.md).
Copy file name to clipboardExpand all lines: articles/certification/program-requirements-pnp.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,7 +24,7 @@ IoT Plug and Play enables solution builders to integrate smart devices with thei
24
24
Promise of IoT Plug and Play certification are:
25
25
26
26
1. Defined device models and interfaces are compliant with the [Digital Twin Definition Language](https://github.com/Azure/opendigitaltwins-dtdl)
27
-
1. Easy integration with Azure IoT based solutions using the [Digital Twin APIs](../iot-develop/concepts-digital-twin.md) : Azure IoT Hub and Azure IoT Central
27
+
1. Easy integration with Azure IoT based solutions using the [Digital Twin APIs](../iot/concepts-digital-twin.md) : Azure IoT Hub and Azure IoT Central
28
28
1. Product truth validated through testing telemetry from end point to cloud using DTDL
29
29
30
30
> [!Note]
@@ -63,7 +63,7 @@ Promise of IoT Plug and Play certification are:
63
63
|**OS**| Agnostic |
64
64
|**Validation Type**| Automated |
65
65
|**Validation**| The [portal workflow](https://certify.azure.com) validates: **1.** Model ID announcement and ensure the device is connected using either the MQTT or MQTT over WebSockets protocol **2.** Models are compliant with the DTDL v2 **3.** Telemetry, properties, and commands are properly implemented and interact between IoT Hub Digital Twin and Device Twin on the device |
**[Required] Device models are published in public model repository**
69
69
@@ -74,7 +74,7 @@ Promise of IoT Plug and Play certification are:
74
74
|**OS**| Agnostic |
75
75
|**Validation Type**| Automated |
76
76
|**Validation**| All device models are required to be published in public repository. Device models are resolved via models available in public repository **1.** User must manually publish the models to the public repository before submitting for the certification. **2.** Note that once the models are published, it is immutable. We strongly recommend publishing only when the models and embedded device code are finalized.*1 *1 User must contact Microsoft support to revoke the models once published to the model repository **3.**[Portal workflow](https://certify.azure.com) checks the existence of the models in the public repository when the device is connected to the certification service |
**[If implemented] Device info Interface: The purpose of test is to validate device info interface is implemented properly in the device code**
@@ -86,7 +86,7 @@ Promise of IoT Plug and Play certification are:
86
86
|**OS**| Agnostic |
87
87
|**Validation Type**| Automated |
88
88
|**Validation**|[Portal workflow](https://certify.azure.com) validates the device code implements device info interface **1.** Checks the values are emitted by the device code to IoT Hub **2.** Checks the interface is implemented in the DCM (this implementation will change in DTDL v2) **3.** Checks properties are not write-able (read only) **4.** Checks the schema type is string and/or long and not null |
89
-
|**Resources**|[Microsoft defined interface](../iot-develop/overview-iot-plug-and-play.md)|
89
+
|**Resources**|[Microsoft defined interface](../iot/overview-iot-plug-and-play.md)|
90
90
|**Azure Recommended**| N/A |
91
91
92
92
**[If implemented] Cloud to device: The purpose of test is to make sure messages can be sent from cloud to devices**
0 commit comments