An Azure machine learning service for building and deploying models.
Hello @Prasanna Sai Kommineni
Yes, you can host a custom-trained SLM in Azure and let edge devices download the model artifact and run inference locally/offline. The key distinction is that you don't need to deploy the model to an Azure online endpoint if inference happens on the device.
A good Azure pattern is:
Training → Azure ML Model Registry / Azure Storage → authenticated model download → local edge runtime
Azure Machine Learning lets you register and version custom models as model assets in a workspace or registry. That gives you centralized model lifecycle/version management in Azure.
For example, after fine-tuning your model, you can register the model artifacts:
az ml model create \
--name my-edge-slm \
--version 1 \
--path ./model \
--type custom_model
The edge application can then download the approved model version during provisioning or an update window and store it locally. Once downloaded, inference can run completely offline using a runtime appropriate to the model format.
For the on-device runtime, Foundry Local is also worth considering. Microsoft describes it specifically as an on-device AI solution where models execute locally, user data stays on the device, and applications can continue operating without network connectivity.
If your devices are IoT/industrial edge devices, Microsoft also documents an Azure IoT Edge architecture where an IoT Edge module downloads an AI model and performs inference locally; ONNX and other optimized model formats are commonly used for this pattern.
So I would choose between:
- Azure ML Model Registry - best when you want model versioning, governance, and MLOps.
- Azure Blob Storage - simpler when you primarily need a secure model-download repository.
- Foundry Local - useful when the target application/device supports Microsoft's local AI runtime.
- Azure IoT Edge - useful when these are managed IoT/industrial edge devices.
One practical point: make sure the model is actually suitable for the target hardware. A Hugging Face/PyTorch model might need conversion or quantization to something like ONNX or another optimized local format before deployment to CPU/NPU-constrained devices.
You also don't have to expose the model publicly. You can protect the download location using Microsoft Entra ID/managed identity, SAS tokens, or another authenticated distribution mechanism.
Sharing these references with you:
Microsoft Learn – Register and manage Azure ML models.
https://learn.microsoft.com/en-us/azure/machine-learning/how-to-manage-models?view=azureml-api-2
Microsoft Learn – Foundry Local for offline/on-device AI.
https://learn.microsoft.com/en-us/azure/foundry-local/what-is-foundry-local
Microsoft Learn – Machine learning inference with Azure IoT Edge.
https://learn.microsoft.com/en-us/azure/architecture/guide/iot/machine-learning-inference-iot-edge
Microsoft Learn – Azure ML registries for sharing/versioning models.
Please "Accept the Answer" if this information helped you. This will help us and others in the community.