IoT Hub Device Provisioning Service (DPS) for Azure IoT Central (SaaS)
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
How to provision devices into IoT Central using DPS?
Documentation says that there is an advanced option available to provision device directly to IoT central.
But when i check in DPS application, there is no option to link to IOT contral.
I am new to IOT development.
azure-iot-hub azure-iot-central microsoft-iot-central
asked Nov 22 '18 at 10:59
RajRaj
1981315
add a comment |
How to provision devices into IoT Central using DPS?
Documentation says that there is an advanced option available to provision device directly to IoT central.
But when i check in DPS application, there is no option to link to IOT contral.
I am new to IOT development.
azure-iot-hub azure-iot-central microsoft-iot-central
asked Nov 22 '18 at 10:59
RajRaj
1981315
add a comment |
How to provision devices into IoT Central using DPS?
Documentation says that there is an advanced option available to provision device directly to IoT central.
But when i check in DPS application, there is no option to link to IOT contral.
I am new to IOT development.
azure-iot-hub azure-iot-central microsoft-iot-central
asked Nov 22 '18 at 10:59
RajRaj
1981315
How to provision devices into IoT Central using DPS?
Documentation says that there is an advanced option available to provision device directly to IoT central.
But when i check in DPS application, there is no option to link to IOT contral.
I am new to IOT development.
azure-iot-hub azure-iot-central microsoft-iot-central
azure-iot-hub azure-iot-central microsoft-iot-central
asked Nov 22 '18 at 10:59
RajRaj
1981315
asked Nov 22 '18 at 10:59
RajRaj
1981315
asked Nov 22 '18 at 10:59
RajRaj
1981315
asked Nov 22 '18 at 10:59
RajRaj
1981315
asked Nov 22 '18 at 10:59
RajRaj
1981315
1981315
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
Azure IoT Central provisions Device Provisioning Service (DPS) when an application is created. The details that will be required to provision your devices can all be retrieved from within your Azure IoT Central application. Based on your use-case, follow these instructions to connect the devices to IoT Central:
- Connect a single device quickly (using Shared Access Signatures)
Connect devices at scale using Shared Access Signatures (SAS)- Connect devices at scale using X509 certificates recommended for production workloads
- Connect without first registering devices
answered Nov 26 '18 at 19:31
Ankit Gupta - MSFTAnkit Gupta - MSFT
563
add a comment |
You can look into following example - https://github.com/Azure/iotc-device-bridge/blob/master/IoTCIntegration/lib/engine.js line 119
const sasToken = await getRegistrationSasToken(context, deviceId);
const registrationOptions = {
url: `https://${registrationHost}/${context.idScope}/registrations/${deviceId}/register?api-version=${registrationApiVersion}`,
method: 'PUT',
json: true,
headers: { Authorization: sasToken },
body: { registrationId: deviceId }
};
answered Mar 7 at 23:00
George TrifonovGeorge Trifonov
1,5351218
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53429463%2fiot-hub-device-provisioning-service-dps-for-azure-iot-central-saas%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Azure IoT Central provisions Device Provisioning Service (DPS) when an application is created. The details that will be required to provision your devices can all be retrieved from within your Azure IoT Central application. Based on your use-case, follow these instructions to connect the devices to IoT Central:
- Connect a single device quickly (using Shared Access Signatures)
Connect devices at scale using Shared Access Signatures (SAS)- Connect devices at scale using X509 certificates recommended for production workloads
- Connect without first registering devices
answered Nov 26 '18 at 19:31
Ankit Gupta - MSFTAnkit Gupta - MSFT
563
add a comment |
Azure IoT Central provisions Device Provisioning Service (DPS) when an application is created. The details that will be required to provision your devices can all be retrieved from within your Azure IoT Central application. Based on your use-case, follow these instructions to connect the devices to IoT Central:
- Connect a single device quickly (using Shared Access Signatures)
Connect devices at scale using Shared Access Signatures (SAS)- Connect devices at scale using X509 certificates recommended for production workloads
- Connect without first registering devices
answered Nov 26 '18 at 19:31
Ankit Gupta - MSFTAnkit Gupta - MSFT
563
add a comment |
Azure IoT Central provisions Device Provisioning Service (DPS) when an application is created. The details that will be required to provision your devices can all be retrieved from within your Azure IoT Central application. Based on your use-case, follow these instructions to connect the devices to IoT Central:
- Connect a single device quickly (using Shared Access Signatures)
Connect devices at scale using Shared Access Signatures (SAS)- Connect devices at scale using X509 certificates recommended for production workloads
- Connect without first registering devices
answered Nov 26 '18 at 19:31
Ankit Gupta - MSFTAnkit Gupta - MSFT
563
Azure IoT Central provisions Device Provisioning Service (DPS) when an application is created. The details that will be required to provision your devices can all be retrieved from within your Azure IoT Central application. Based on your use-case, follow these instructions to connect the devices to IoT Central:
- Connect a single device quickly (using Shared Access Signatures)
Connect devices at scale using Shared Access Signatures (SAS)- Connect devices at scale using X509 certificates recommended for production workloads
- Connect without first registering devices
answered Nov 26 '18 at 19:31
Ankit Gupta - MSFTAnkit Gupta - MSFT
563
answered Nov 26 '18 at 19:31
Ankit Gupta - MSFTAnkit Gupta - MSFT
563
answered Nov 26 '18 at 19:31
Ankit Gupta - MSFTAnkit Gupta - MSFT
563
answered Nov 26 '18 at 19:31
Ankit Gupta - MSFTAnkit Gupta - MSFT
563
563
add a comment |
add a comment |
You can look into following example - https://github.com/Azure/iotc-device-bridge/blob/master/IoTCIntegration/lib/engine.js line 119
const sasToken = await getRegistrationSasToken(context, deviceId);
const registrationOptions = {
url: `https://${registrationHost}/${context.idScope}/registrations/${deviceId}/register?api-version=${registrationApiVersion}`,
method: 'PUT',
json: true,
headers: { Authorization: sasToken },
body: { registrationId: deviceId }
};
answered Mar 7 at 23:00
George TrifonovGeorge Trifonov
1,5351218
add a comment |
You can look into following example - https://github.com/Azure/iotc-device-bridge/blob/master/IoTCIntegration/lib/engine.js line 119
const sasToken = await getRegistrationSasToken(context, deviceId);
const registrationOptions = {
url: `https://${registrationHost}/${context.idScope}/registrations/${deviceId}/register?api-version=${registrationApiVersion}`,
method: 'PUT',
json: true,
headers: { Authorization: sasToken },
body: { registrationId: deviceId }
};
answered Mar 7 at 23:00
George TrifonovGeorge Trifonov
1,5351218
add a comment |
You can look into following example - https://github.com/Azure/iotc-device-bridge/blob/master/IoTCIntegration/lib/engine.js line 119
const sasToken = await getRegistrationSasToken(context, deviceId);
const registrationOptions = {
url: `https://${registrationHost}/${context.idScope}/registrations/${deviceId}/register?api-version=${registrationApiVersion}`,
method: 'PUT',
json: true,
headers: { Authorization: sasToken },
body: { registrationId: deviceId }
};
answered Mar 7 at 23:00
George TrifonovGeorge Trifonov
1,5351218
You can look into following example - https://github.com/Azure/iotc-device-bridge/blob/master/IoTCIntegration/lib/engine.js line 119
const sasToken = await getRegistrationSasToken(context, deviceId);
const registrationOptions = {
url: `https://${registrationHost}/${context.idScope}/registrations/${deviceId}/register?api-version=${registrationApiVersion}`,
method: 'PUT',
json: true,
headers: { Authorization: sasToken },
body: { registrationId: deviceId }
};
answered Mar 7 at 23:00
George TrifonovGeorge Trifonov
1,5351218
answered Mar 7 at 23:00
George TrifonovGeorge Trifonov
1,5351218
answered Mar 7 at 23:00
George TrifonovGeorge Trifonov
1,5351218
answered Mar 7 at 23:00
George TrifonovGeorge Trifonov
1,5351218
1,5351218
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53429463%2fiot-hub-device-provisioning-service-dps-for-azure-iot-central-saas%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
