You've uploaded your own or generated the device certificates on your device if you changed the device name or the DNS domain via the Device page. If you haven't done this step, you'll see an error during the device activation and the activation will be blocked. For more information, go to Configure certificates.
You have the activation key from the Azure Stack Edge service that you created to manage the Azure Stack Edge Pro device. For more information, go to Prepare to deploy Azure Stack Edge Pro.
Activate the device
In the local web UI of the device, go to Get started page.
First the device is activated. You're then prompted to download the key file.
Select Download and continue and save the device-serial-no.json file in a safe location outside of the device. This key file contains the recovery keys for the OS disk and data disks on your device. These keys may be needed to facilitate a future system recovery.
Here are the contents of the json file:
JSON
{
"Id": "<Device ID>",
"DataVolumeBitLockerExternalKeys": {
"hcsinternal": "<BitLocker key for data disk>",
"hcsdata": "<BitLocker key for data disk>"
},
"SystemVolumeBitLockerRecoveryKey": "<BitLocker key for system volume>",
"ServiceEncryptionKey": "<Azure service encryption key>"
}
The following table explains the various keys:
Field
Description
Id
This is the ID for the device.
DataVolumeBitLockerExternalKeys
These are the BitLocker keys for the data disks and are used to recover the local data on your device.
SystemVolumeBitLockerRecoveryKey
This is the BitLocker key for the system volume. This key helps with the recovery of the system configuration and system data for your device.
ServiceEncryptionKey
This key protects the data flowing through the Azure service. This key ensures that a compromise of the Azure service won't result in a compromise of stored information.
Go to the Overview page. The device state should show as Activated.
The device activation is complete. You can now add shares on your device.
To deploy network functions as managed applications:
Make sure that you create a Device resource for Azure Network Function Manager (NFM) that is linked to the Azure Stack Edge resource. The device resource aggregates all the network functions deployed on Azure Stack Edge device. For detailed instructions, see Tutorial: Create a Network Function Manager Device resource (Preview).
After a Kubernetes cluster is created on your Azure Stack Edge device, you can deploy application workloads on this cluster via any of the following methods: