Use a config file to deploy an Azure Stack Edge device
APPLIES TO: 
Azure Stack Edge Pro - GPUAzure Stack Edge Pro 2Azure Stack Edge Pro RAzure Stack Edge Mini R
This article describes how to use PowerShell to automate initial device configuration and activation of Azure Stack Edge devices. Use the steps in this article as alternatives to the local web user interface setup sequence.
You can run as many rounds of device configuration as necessary. You can also use the Azure portal or the device local user interface to modify device configuration.
Usage considerations
- You can apply individual configuration changes to a device using PowerShell cmdlets, or you can apply bulk configuration changes using a JSON file.
- You can apply changes with a JSON file at any point in the appliance lifecycle.
- To manage devices using the local web user interface, see Connect to Azure Stack Edge Pro with GPU.
- You can't change device authentication using this method. To change device authentication settings, see Change device password.
- Cluster formation is not supported using PowerShell cmdlets. For more information about Azure Stack Edge clusters, see Install a two-node cluster.
About device setup and configuration
Device setup and configuration declarations define the configuration for that device using a root-level "Device" identifier. Declarations supported for Azure Stack Edge devices include:
- Device endpoint
- Password
- Certificates
- Encryption at rest
- Web proxy
- Network
- Time
- Update
- Virtual IP configuration
- Proactive log consent
- Device activation
A device configuration operation doesn't have to include every declaration; you can include only the declarations that create a desired configuration for your device.
The following PowerShell cmdlets are supported to configure Azure Stack Edge devices:
| Cmdlet | Description |
|---|---|
| Set-Login | First-time sign in, set or change sign in credentials to access the device. |
| Get-DeviceConfiguration | Fetch the current device configuration. |
| Set-DeviceConfiguration | Change the device configuration. |
| New-Package | Prepare a device setup configuration package to apply to one or more devices. |
| Get-DeviceConfigurationStatus | Fetch the status of in-progress configuration changes being applied to the device to determine whether the operation succeeded, failed, or is still in progress. |
| Get-DeviceDiagnostic | Fetch diagnostic status of the device. |
| Start-DeviceDiagnostic | Start a new diagnostic run to verify status after a device setup configuration package has been applied. |
| To-json | A utility command that formats the cmdlet response in a JSON file. |
| Get-DeviceLogConsent | Fetch the proactive log consent setting for the device. |
| Set-DeviceLogConsent | Set the proactive log consent setting for the device. |
| Get-DeviceVip | Fetch virtual IP configuration for your Azure Stack Edge two-node cluster. |
| Set-DeviceVip | Set the virtual IP configuration for your Azure Stack Edge two-node cluster. |
Prerequisites
Before you begin, make sure that you:
- Have a client running Windows 10 or later, or Windows Server 2016 or later.
- Are running PowerShell version 5.1 or later.
- Are connected to the local web UI of an Azure Stack Edge device. For more information, see Connect to Azure Stack Edge Pro with GPU.
- Have downloaded the PowerShell module.
Import the module and sign in to the device
Use the following steps to import the PowerShell module and sign in to the device.
Run PowerShell as an administrator.
Import the PowerShell module.
Import-Module "<Local path to PowerShell module>"\PowerShellBasedConfiguration.psm1Sign in to the device using the
Set-Logincmdlet. First-time sign-in requires a password reset usingNewPassword.Set-Login "https://<IP address>" "<Password1>" "<NewPassword>"
Fetch the device configuration
Use the following cmdlet to fetch the device configuration:
Get-DeviceConfiguration | To-json
Apply initial configuration to a device
Use the following steps to create a device configuration package in PowerShell and then apply the configuration to one or more devices.
Run the following cmdlets in PowerShell:
Set the
timeobject property.$time = New-Object PSObject -Property @{ TimeZone = "Hawaiian Standard Time" }Set the
updateobject property.$update = New-Object PSObject -Property @{ ServerType = "MicrosoftUpdate" }Create a package with the new
timeandupdatesettings.$pkg = New-Package -Time $time -Update $updateRun the package.
$newCfg = Set-DeviceConfiguration -DesiredDeviceConfig $pkgVerify that the operation is complete.
Get-DeviceConfigurationStatus | To-jsonHere's sample output:
PS C:\> Get-DeviceConfigurationStatus | To-json { "deviceConfiguration": { "status": "Complete", "results": [ { "declarationName": "Time", "resultCode": "Success", "errorCode": "None", "message": null }, { "declarationName": "Update", "resultCode": "Success", "errorCode": "None", "message": null } ] } } PS C:\>After the operation is complete, fetch the new device configuration.
Get-DeviceConfiguration | To-jsonSave the device configuration as a JSON file.
Get-DeviceConfiguration | To-json | Out-File "<Local path>\TestConfig2.json"After saving device configuration settings to a JSON file, you can use steps in the following section to use the JSON file to apply those device configuration settings to one or more devices.
Update a device using a JSON file, without device activation
Once a config.json file has been created, as shown in the previous example, with the desired configuration, use the JSON file to change configuration settings on one or more devices.
Note
Use a config.json file that meets the needs of your organization. Sample JSON files are available here.
Configure a single-node device
This sequence of PowerShell cmdlets signs in to the device, applies device configuration settings from a JSON file, verifies completion of the operation, and then fetches the new device configuration.
Run the following cmdlets in PowerShell:
Before you run the device configuration operation, ensure that the JSON file uses the
nodeNameof the device to be changed.Note
Each device has a unique
nodeName. To change device configuration settings, thenodeNamein the JSON file must match thenodeNameof the device to be changed.Fetch the
nodeNamefrom the device with the following command in PowerShell:Get-DeviceConfiguration | To-jsonHere's sample output showing
nodeNamefor the device:PS C:\> Get-DeviceConfiguration | To-json { "device": { "deviceInfo": { "model": "Azure Stack Edge", "softwareVersion": "2.2.2075.5523", "serialNumber": "1HXQG13", "isActivated": false, "nodes": [ { "id": "d0d8cb16-60d4-4970-bb65-b9d254d1a289", "name": "1HXQG13" } ] }, } }Create a package that uses a local JSON file for device configuration settings.
$p = Get-Content -Path "<Local path>\<ConfigFileName.json>" | ConvertFrom-jsonRun the package.
$newCfg = Set-DeviceConfiguration -DesiredDeviceConfig $pMonitor status of the operation. It may take 10 minutes or more for the changes to complete.
Get-DeviceConfigurationStatus | To-jsonAfter the operation is complete, fetch the new device configuration.
Get-DeviceConfiguration | To-json
Configure a two-node device
This sequence of PowerShell cmdlets applies device configuration settings from a JSON file, verifies completion of the operation, and then fetches the new device configuration.
Note
Two-node configurations are only supported on Azure Stack Edge Pro GPU and Azure Stack Edge Pro 2 devices.
Run the following cmdlets in PowerShell:
Before you run the device configuration operation, ensure that the JSON file uses the
nodeNameof the device to be changed.Note
Each device has a unique
nodeName. To change device configuration settings, thenodeNamein the JSON file must match thenodeNameof the device to be changed.Fetch the
nodeNamefrom the device with the following command in PowerShell:Get-DeviceConfiguration | To-jsonHere's sample output showing
nodeNamefor the device:PS C:\> Get-DeviceConfiguration | To-json { "device": { "deviceInfo": { "model": "Azure Stack Edge", "softwareVersion": "2.2.2075.5523", "serialNumber": "1HXQG13", "isActivated": false, "nodes": [ { "id": "d0d8cb16-60d4-4970-bb65-b9d254d1a289", "name": "1HXQG13" } ] }, } }Create a package that uses a local JSON file for device configuration settings.
$p = Get-Content -Path "<Local path>\<ConfigFileName-two-node-device.json>" | ConvertFrom-jsonRun the package.
$newCfg = Set-DeviceConfiguration -DesiredDeviceConfig $pMonitor status of the operation. It may take 10 minutes or more for the changes to complete.
Get-DeviceConfigurationStatus | To-jsonAfter the operation is complete, fetch the new device configuration.
Get-DeviceConfiguration | To-jsonHere's sample output:
PS C:\> Get-DeviceConfiguration | To-json { "device": { "deviceInfo": { "model": "Azure Stack Edge", "softwareVersion": "3.2.2380.1548", "serialNumber": "1HXG613", "isActivated": true, "nodes": [ { "id": "9b1817b9-67f5-4631-8466-447b89b829f3", "name": "HW6C1T2" }, { "id": "b4eeebad-9395-4aa8-b6b4-2f2d66eccf58", "name": "1HXG613" } ] }, "deviceEndpoint": { "name": "DBE-1HXG613", "dnsDomain": "microsoftdatabox.com" }, "encryptionAtRestKeys": null, "network": { "dhcpPolicy": "AttemptRenew", "interfaces": [ { "name": "Port1", "nodeName": "1HXG613", "nodeId": "b4eeebad-9395-4aa8-b6b4-2f2d66eccf58", "isDhcpEnabled": false, "iPv4": { "address": "192.0.2.0/24", "subnetMask": "255.255.255.0", "gateway": null }, "iPv6": null, "dnsServerAddresses": null, "dnsSuffix": null, "routes": null, "ipConfigType": "IP" }, { "name": "Port1", "nodeName": "HW6C1T2", "nodeId": "9b1817b9-67f5-4631-8466-447b89b829f3", "isDhcpEnabled": false, "iPv4": { "address": "192.0.2.0/24", "subnetMask": "255.255.255.0", "gateway": null }, "iPv6": null, "dnsServerAddresses": null, "dnsSuffix": null, "routes": null, "ipConfigType": "IP" }, { "name": "Port2", "nodeName": "1HXG613", "nodeId": "b4eeebad-9395-4aa8-b6b4-2f2d66eccf58", "isDhcpEnabled": true, "iPv4": { "address": "192.0.2.0/24", "subnetMask": "255.255.248.0", "gateway": "10.126.72.1" }, "iPv6": null, "dnsServerAddresses": [ "10.50.50.50", "10.50.10.50" ], "dnsSuffix": "corp.microsoft.com", "routes": null, "ipConfigType": "IP" }, { "name": "Port2", "nodeName": "HW6C1T2", "nodeId": "9b1817b9-67f5-4631-8466-447b89b829f3", "isDhcpEnabled": true, "iPv4": { "address": "192.0.2.0/24", "subnetMask": "255.255.248.0", "gateway": "10.126.72.1" }, "iPv6": null, "dnsServerAddresses": [ "10.50.50.50", "10.50.10.50" ], "dnsSuffix": "corp.microsoft.com", "routes": null, "ipConfigType": "IP" }, { "name": "Port3", "nodeName": "1HXG613", "nodeId": "b4eeebad-9395-4aa8-b6b4-2f2d66eccf58", "isDhcpEnabled": true, "iPv4": { "address": "192.0.2.0/24", "subnetMask": "255.255.0.0", "gateway": null }, "iPv6": null, "dnsServerAddresses": [ "192.168.0.1" ], "dnsSuffix": "wdshcsso.com", "routes": null, "ipConfigType": "IP" }, { "name": "Port3", "nodeName": "HW6C1T2", "nodeId": "9b1817b9-67f5-4631-8466-447b89b829f3", "isDhcpEnabled": true, "iPv4": { "address": "192.0.2.0/24", "subnetMask": "255.255.0.0", "gateway": null }, "iPv6": null, "dnsServerAddresses": [ "192.168.0.1" ], "dnsSuffix": "wdshcsso.com", "routes": null, "ipConfigType": "IP" }, { "name": "Port4", "nodeName": "1HXG613", "nodeId": "b4eeebad-9395-4aa8-b6b4-2f2d66eccf58", "isDhcpEnabled": true, "iPv4": { "address": "192.0.2.0/24", "subnetMask": "255.255.0.0", "gateway": null }, "iPv6": null, "dnsServerAddresses": [ "192.168.0.1" ], "dnsSuffix": "wdshcsso.com", "routes": null, "ipConfigType": "IP" }, { "name": "Port4", "nodeName": "HW6C1T2", "nodeId": "9b1817b9-67f5-4631-8466-447b89b829f3", "isDhcpEnabled": true, "iPv4": { "address": "192.168.6.99", "subnetMask": "255.255.0.0", "gateway": null }, "iPv6": null, "dnsServerAddresses": [ "192.168.0.1" ], "dnsSuffix": "wdshcsso.com", "routes": null, "ipConfigType": "IP" }, { "name": "Port5", "nodeName": "1HXG613", "nodeId": "b4eeebad-9395-4aa8-b6b4-2f2d66eccf58", "isDhcpEnabled": true, "iPv4": { "address": "192.0.2.0/24", "subnetMask": "255.255.0.0", "gateway": null }, "iPv6": null, "dnsServerAddresses": [ "192.168.0.1" ], "dnsSuffix": "wdshcsso.com", "routes": null, "ipConfigType": "IP" }, { "name": "Port5", "nodeName": "HW6C1T2", "nodeId": "9b1817b9-67f5-4631-8466-447b89b829f3", "isDhcpEnabled": true, "iPv4": { "address": "192.0.2.0/24", "subnetMask": "255.255.0.0", "gateway": null }, "iPv6": null, "dnsServerAddresses": [ "192.168.0.1" ], "dnsSuffix": "wdshcsso.com", "routes": null, "ipConfigType": "IP" }, { "name": "Port6", "nodeName": "1HXG613", "nodeId": "b4eeebad-9395-4aa8-b6b4-2f2d66eccf58", "isDhcpEnabled": true, "iPv4": { "address": "192.0.2.0/24", "subnetMask": "255.255.0.0", "gateway": null }, "iPv6": null, "dnsServerAddresses": [ "192.168.0.1" ], "dnsSuffix": "wdshcsso.com", "routes": null, "ipConfigType": "IP" }, { "name": "Port6", "nodeName": "HW6C1T2", "nodeId": "9b1817b9-67f5-4631-8466-447b89b829f3", "isDhcpEnabled": true, "iPv4": { "address": "192.0.2.0/24", "subnetMask": "255.255.0.0", "gateway": null }, "iPv6": null, "dnsServerAddresses": [ "192.168.0.1" ], "dnsSuffix": "wdshcsso.com", "routes": null, "ipConfigType": "IP" } ], "vSwitches": [ { "name": "vSwitch1", "interfaceName": [ "Port2" ], "enabledForCompute": true, "enabledForStorage": false, "enabledForMgmt": true, "supportsAcceleratedNetworking": false, "enableEmbeddedTeaming": true, "ipAddressPools": [ { "name": "KubernetesNodeIPs", "ipAddressRange": "10.126.75.200-10.126.75.202" }, { "name": "KubernetesServiceIPs", "ipAddressRange": "10.126.75.206-10.126.75.208" } ], "mtu": 1500 }, { "name": "vSwitch2", "interfaceName": [ "Port3" ], "enabledForCompute": false, "enabledForStorage": true, "enabledForMgmt": false, "supportsAcceleratedNetworking": false, "enableEmbeddedTeaming": true, "ipAddressPools": [ ], "mtu": 1500 }, { "name": "TestvSwitch", "interfaceName": [ "Port5" ], "enabledForCompute": false, "enabledForStorage": false, "enabledForMgmt": false, "supportsAcceleratedNetworking": true, "enableEmbeddedTeaming": false, "ipAddressPools": [ ], "mtu": 9000 } ], "virtualNetworks": [ { "name": "TestvSwitch-internal", "vSwitchName": "TestvSwitch", "vlanId": 0, "subnetMask": "255.255.255.0", "gateway": "192.0.2.0/24", "network": "192.0.2.0/24", "enabledForKubernetes": false, "ipAddressPools": [ { "name": "VirtualMachineIPs", "ipAddressRange": "192.0.2.0/24" } ] } ] }, "time": { "timeZone": "Pacific Standard Time", "primaryTimeServer": "time.windows.com", "secondaryTimeServer": null }, "update": { "serverType": "None", "wsusServerURI": null }, "webProxy": { "isEnabled": false, "connectionURI": null, "authentication": "None", "username": null, "password": null } } } PS C:\>
Activate a device
Use the following steps to activate an Azure Stack Edge device. Note that activation can't be undone, and a device activation key can't be reused or applied to a different device.
Retrieve the
ActivationKeyfor your device. For detailed steps, see Create a management resource, and Get the activation key.Set the
ActivationKeyproperty.$ActivationKey = "<Activation key>"Create an activation object and set the
ActivationKeyproperty.$activation = New-Object PsObject -Property @{ActivationKey=$ActivationKey; ServiceEncryptionKey=""}Create a package with the activation object and
ActivationKey.$p = New-Package -Activation $activationRun the package.
$newCfg = Set-DeviceConfiguration -DesiredDeviceConfig $pMonitor status of the operation. It may take 10 minutes or more for the changes to complete.
Get-DeviceConfigurationStatus | To-jsonHere's sample output:
PS C:\> Get-DeviceConfigurationStatus | to-json { "deviceConfiguration": { "status": "Complete", "results": [ { "declarationName": "Network", "resultCode": "Success", "errorCode": "None", "message": null }, { "declarationName": "Activation", "resultCode": "Success", "errorCode": "None", "message": null }, { "declarationName": "DeviceEndpoint", "resultCode": "Success", "errorCode": "None", "message": null }, { "declarationName": "WebProxy", "resultCode": "Success", "errorCode": "None", "message": null }, { "declarationName": "Time", "resultCode": "NotExecuted", "errorCode": "None", "message": "" }, { "declarationName": "Update", "resultCode": "NotExecuted", "errorCode": "None", "message": "" } ] } }After the operation is complete, fetch the new device configuration.
Get-DeviceConfiguration | To-jsonHere's sample output showing that the device is activated:
PS C:\> Get-DeviceConfiguration | To-json { "device": { "deviceInfo": { "model": "Azure Stack Edge", "softwareVersion": "2.2.2075.5523", "serialNumber": "1HXQJ23", "isActivated": true, "nodes": [ { "id": "d0d8ca16-60d4-4970-bb65-b9d254d1a289", "name": "1HXQG13" } ] }, } }
Quickly fetch or change device configuration settings
Use the following steps to fetch the status of the WebProxy properties, set the WebProxy property to “isEnabled = true” and set the WebProxy URI, and then fetch the status of the changed WebProxy properties. After running the package, verify the new device configuration.
Load the device configuration cmdlet.
$p = Get-DeviceConfigurationFetch the status of the
WebProxyproperties.$p.device.webproxyHere's sample output:
PS C:\> $p.device.webproxy isEnabled : False connectionURI : null authentication : None username : password :Set the
WebProxyproperty to “isEnabled = true” and set theWebProxyURI.$p.device.webproxy.isEnabled = $true $p.device.webproxy.connectionURI = "<specify a URI depending on the geographic location of the device>"Fetch the status of the updated
WebProxyproperties.$p.device.webproxyHere's sample output:
PS C:\> $p.device.webproxy isEnabled : True connectionURI : http://10.57.48.82:8080 authentication : None username : password :Run the package with updated
WebProxyproperties.$newCfg = Set-DeviceConfiguration -DesiredDeviceConfig $pMonitor status of the operation. It may take 10 minutes or more for the changes to complete.
Get-DeviceConfigurationStatus | To-jsonAfter the operation is complete, fetch the new device configuration.
Get-DeviceConfiguration | To-jsonHere's sample output:
"webProxy": { "isEnabled": true, "connectionURI": "http://10.57.48.82:8080", "authentication": "None", "username": null, "password": null }
Enable proactive log collection
Proactive log collection gathers system health indicators on your Azure Stack Edge device to help you efficiently troubleshoot any device issues. Proactive log collection is enabled by default. For more information, see Proactive log collection.
Use the following steps to fetch the current setting and then enable or disable proactive logging for your device.
Fetch the device configuration.
Get-DeviceConfiguration | To-jsonEnable device log consent.
Set-DeviceLogConsent -logConsent $trueHere's sample output:
PS C:\> Get-DeviceLogConsent False PS C:\> Set-DeviceLogConsent -logConsent $true True PS C:\> Get-DeviceLogConsent True PS C:\>Fetch the device log consent configuration.
Get-DeviceLogConsent
Run device diagnostics
To diagnose and troubleshoot device errors, run diagnostic tests. For more information, see Run diagnostics.
Use the following steps to verify device status after you apply a configuration package.
Run device diagnostics.
Start-DeviceDiagnosticFetch status of the device diagnostics operation.
Get-DeviceDiagnostic | To-jsonHere's sample output:
PS C:\> Get-DeviceDiagnostic | To-json { "lastRefreshTime": "2022-09-27T20:12:10.643768Z", "status": "Complete", "diagnostics": [ { "test": "System software", "category": "Software", "status": "Succeeded", "recommendedActions": "" }, { "test": "Disks", "category": "Hardware, Disk", "status": "Succeeded", "recommendedActions": "" }, { "test": "Power Supply Units", "category": "Hardware", "status": "Succeeded", "recommendedActions": "" }, { "test": "Network interfaces", "category": "Hardware", "status": "Succeeded", "recommendedActions": "" }, { "test": "CPUs", "category": "Hardware", "status": "Succeeded", "recommendedActions": "" }, { "test": "Network settings ", "category": "Logical, Network", "status": "Succeeded", "recommendedActions": "" }, { "test": "Internet connectivity", "category": "Logical, Network", "status": "Succeeded", "recommendedActions": "" }, { "test": "Web proxy", "category": "Logical, Network", "status": "NotApplicable", "recommendedActions": "" }, { "test": "Time sync ", "category": "Logical, Time", "status": "Succeeded", "recommendedActions": "" }, { "test": "Azure portal connectivity", "category": "Logical, Network, AzureConnectivity", "status": "Succeeded", "recommendedActions": "" }, { "test": "Azure storage account credentials", "category": "Logical, AzureConnectivity", "status": "NotApplicable", "recommendedActions": "" }, { "test": "Software update readiness", "category": "Logical, Update", "status": "Succeeded", "recommendedActions": "" }, { "test": "User passwords", "category": "Logical, PasswordExpiry", "status": "Succeeded", "recommendedActions": "" }, { "test": "Azure consistent services health check", "category": "ACS", "status": "Succeeded", "recommendedActions": "" }, { "test": "Certificates", "category": "Certificates", "status": "Succeeded", "recommendedActions": "" }, { "test": "Azure container read/write", "category": "Logical, Network, AzureConnectivity", "status": "NotApplicable", "recommendedActions": "" }, { "test": "Azure Edge compute runtime", "category": "Logical, AzureEdgeCompute", "status": "Succeeded", "recommendedActions": "" }, { "test": "Compute acceleration", "category": "Hardware, Logical", "status": "Succeeded", "recommendedActions": "" } ] }
Set the virtual IP configuration on a two-node device
Note
Two-node configurations are only supported on Azure Stack Edge Pro GPU and Azure Stack Edge Pro 2 devices.
A virtual IP is an available IP in the cluster network. Set a virtual IP to connect to a clustered device instead of an individual node. Any client connecting to the cluster network on the two-node device must be able to access the virtual IP.
You can set either an Azure Consistent Services or a Network File System configuration. Additional options include static or DHCP network settings. For more information about setting virtual IPs, see Configure virtual IPs.
Set a static Azure Consistent Services configuration
Fetch the
DeviceVIPconfiguration.Get-DeviceVip | to-jsonSet the
DeviceVIPproperty with a static Azure Consistent Services configuration.$acsVip = New-Object PSObject -Property @{ Type = "ACS"; VipAddress = "10.57.51.32"; ClusterNetworkAddress = "10.57.48.0"; IsDhcpEnabled = $false }Update the device with the
DeviceVIPproperty.Set-DeviceVip -vip $acsVipFetch the updated
DeviceVIPconfiguration.Get-DeviceVip | to-jsonHere's sample output:
{ "acsVIP": { "type": "ACS", "name": "Azure Consistent Services", "address": "10.57.51.32", "network": { "name": "Cluster Network 3", "address": "10.57.48.0", "subnet": "255.255.248.0", "dhcpEnabled": false }, "isDhcpEnabled": false } } PS C:\>
Set a DHCP Azure Consistent Services configuration
Fetch the
DeviceVIPconfiguration.Get-DeviceVip | to-jsonSet the
DeviceVIPproperty to enable DHCP.$acsVip = New-Object PSObject -Property @{ Type = "ACS"; VipAddress = $null; ClusterNetworkAddress = "10.57.48.0"; IsDhcpEnabled = $true }Update the device with the
DeviceVIPproperty.Set-DeviceVip -vip $acsVipFetch the updated
DeviceVIPconfiguration.Get-DeviceVip | to-jsonHere's sample output:
{ "acsVIP": { "type": "ACS", "name": "Azure Consistent Services", "address": "10.57.53.225", "network": { "name": "Cluster Network 3", "address": "10.57.48.0", "subnet": "255.255.248.0", "dhcpEnabled": true }, "isDhcpEnabled": true }, } PS C:\>
Troubleshooting
Next steps
Feedback
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see: https://aka.ms/ContentUserFeedback.
Submit and view feedback for