1. #AzConfDev
Azure IoT Central
Marco Parenzan
is interesting…

2. #AzConfDev
Azure IoT Central
Marco Parenzan
is NOT a toy…

3. #AzConfDev
Marco Parenzan
Senior Solution Architect @ beanTech

4. #AzConfDev
Marco Parenzan
Senior Solution Architect in beanTech
Microsoft Azure MVP
Community Lead 1nn0va // Pordenone
1nn0va After Hour
weekly, every Thuesday evening 9PM CET
https://bit.ly/1nn0va-video
Linkedin: https://www.linkedin.com/in/marcoparenzan/
nov 20, 2022

5. #AzConfDev
The reality of IoT is…
Building globally secure, scalable and
reliable IoT solutions is incredibly
complex. At least 30% of all companies
do not move beyond proof of concept,
due to complexity, high costs, lack of
staff, and concerns around security.
Designing successful IoT systems from
the ground up can require selecting,
configuring and managing dozens of
services
There is a significant skills gap around
IoT, which requires expertise across IT,
OT an, Security, and other services.
The customer looks only on the device
and the field…

6. #AzConfDev
Why Azure IoT Central is interesting and not a toy
• It is fully compliant with Azure IoT Platform (Azure IoT Hub, Azure IoT Device
Provisioning Services, Azure IoT Device)
• It has an interesting pricing model (per Device)
• It forces you in terms of modeling (Device Twin and Plug and Play)
• It gives you a fast start...
• ...because it is a very interesting scenario based tool...
• ...with standard that gives you a growth path!
• It is extensible with other Azure services
• It shows how an IoT Solution should be

7. #AzConfDev
Why Azure IoT Central is interesting
• It is fully compliant with Azure IoT Platform (Azure IoT Hub, Azure IoT Device
Provisioning Services, Azure IoT Device)
• It has an interesting pricing model (per Device)
• It forces you in terms of modeling (Device Twin and Plug and Play)
• It gives you a fast start...
• ...because it is a very interesting scenario based tool...
• ...with standard that gives you a growth path!
• It is extensible with other Azure services
• It shows how an IoT Solution should be
• It can help lot of companies to become OEMs

8. #AzConfDev
OEMs
• Open Equipment Manifactures
• It means a couple of things
• They create devices for someone else (they are not the end
users of devices) in a product manner
• They work directly or through partner
• At every level they need an app, the same app, a different app,
some different roles

9. #AzConfDev
OEMs
• Open Equipment Manifactures
• It means a couple of things
• They create devices for someone else (they are not the end
users of devices) in a product manner
• They work directly or through partner
• At every level they need an app, the same app, a different app,
some different roles
• This is something that allow lowering the barries for (at least)
medium sized companies, but also brave small companies
• In a world that is moving towards servitization

10. #AzConfDev
Power BI
PowerApps Web Apps
Mobile Apps
Manage
View and manage solutions
Azure Sphere
Secured MCU Secured OS Cloud Security
Business Integration
Connect to business apps & services
Office 365
Dynamics 365
Edge Modules:
• Protocol Adaptation
• Functions
• Stream Analytics
• Machine Learning
• AI
Azure
IoT Edge
• Integrated view for CISO & SecOps personas to review enterprise security posture, including IoT solutions.
• Holistic view of IoT solution security posture for DevOps and IoT solution managers to review and manage day to day security status
Azure Security
Center for IoT
3rd Party applications
Azure IoT Device SDK
3rd Party Industry specific sensors & devices
(RTOS, Linux, Windows, Android, iOS)
IoT Hub
Container
Registry
Kubernetes
Service
Compute
(VMs)
Content
Delivery
Network
Data
Explorer
Front Door
Resource
Manager
(ARM)
Storage
Domain
Name
System
Microsoft
Flow
Key Vault
Service Bus
Application
Insights
Functions
SQL Azure
Cosmos DB
Web Apps
Azure Stream
Analytics
Event Hub
Device
Provisioning
Service Time Series
Insights
Maps
Your (scary!) options for building IoT solutions
 Predictable pricing
 Industry-focused

11. #AzConfDev
Power BI
PowerApps Web Apps
Mobile Apps
Manage
View and manage solutions
Azure Sphere
Secured MCU Secured OS Cloud Security
Business Integration
Connect to business apps & services
Office 365
Dynamics 365
Edge Modules:
• Protocol Adaptation
• Functions
• Stream Analytics
• Machine Learning
• AI
Azure
IoT Edge
• Integrated view for CISO & SecOps personas to review enterprise security posture, including IoT solutions.
• Holistic view of IoT solution security posture for DevOps and IoT solution managers to review and manage day to day security status
Azure Security
Center for IoT
3rd Party applications
Azure IoT Device SDK
3rd Party Industry specific sensors & devices
(RTOS, Linux, Windows, Android, iOS)
The opportunity of Azure IoT Central

12. #AzConfDev
Let’s look into specific topics

13. #AzConfDev
Device Management
• It forces you in terms of modeling
• Templates (Digital Twins) Device Twin and Plug and Play
• Device Provisioning Service
• Versioning
• Dashboard

14. #AzConfDev
Pricing Model
Standard Tier 0 Standard Tier 1 Standard Tier 2
Price per device
€0,07 al mese €0,34 al mese €0,59 al mese
Monthly device message allocation* 400 messages 5,000 messages 30,000 messages
Included free quantity per IoT Central
application
2 free devices
(800 included messages)
2 free devices
(10,000 included messages)
2 free devices
(60,000 included messages)
Use case For devices sending a few messages per
hour
For devices sending a few messages per
hour
For devices sending a message every
few minutes
Overage pricing per 1K messages1 €0.060 per 1K messages €0.013 per 1K messages €0.013 per 1K messages
*Total message allocation is shared across all devices in an IoT Central application

15. #AzConfDev
API for external integration
• This is the most specific/custom part of IoT Central
• Something you will have to throw away if you growth to IoT Hub
• (some of) it is built on EventHub and Stream Analytics
• But with the correct way to do that!
• The other way is...

16. #AzConfDev
Route, not (only) Stream
Route first=Segregate messages on their meaning
Process single messages (not only time window aggregation)

17. #AzConfDev
“Build with” patterns (from Industry
Application Templates)

18. #AzConfDev
(extreme) compatibility with Azure IoT
• The code you write is exactly the same
• The routing infrastructure is exactly the same
• So evolution to full IoT Hub-based platform, is just an upgrade to what you
have not implemented

19. #AzConfDev
Organizations
You can build an hiearchy in organization
Different people (from different companies) with different roles
All users authenticate through AAD authentication (even if with no specific control)
It starts lowering the barries to access this kind of solution
This is the other part you probably you have to work on...

20. #AzConfDev
Conclusions
If you don’t know where to start with IoT, Azure IoT Central is the correct starting point
You have to add ONLY what is really related to your business

21. #AzConfDev
THANK YOU! NOW Q&A
Azure IoT Central
Marco Parenzan
Senior Software Architect @
beanTech
Senior Solution Architect in beanTech
Microsoft Azure MVP
Community Lead 1nn0va // Pordenone ITALY
1nn0va After Hour
https://bit.ly/1nn0va-video
Linkedin: https://www.linkedin.com/in/marcoparenzan/