Storing Data Azure Iot Central
can I access to the Iot Hub behind the Azure Iot Central? I need to use:
- IoT Edge feature
- Device Provisioning
- Get to Event-Hub Endpoint to process data
Cheers
azure azure-iot-hub azure-iot-edge azure-iot-central
add a comment |
can I access to the Iot Hub behind the Azure Iot Central? I need to use:
- IoT Edge feature
- Device Provisioning
- Get to Event-Hub Endpoint to process data
Cheers
azure azure-iot-hub azure-iot-edge azure-iot-central
add a comment |
can I access to the Iot Hub behind the Azure Iot Central? I need to use:
- IoT Edge feature
- Device Provisioning
- Get to Event-Hub Endpoint to process data
Cheers
azure azure-iot-hub azure-iot-edge azure-iot-central
can I access to the Iot Hub behind the Azure Iot Central? I need to use:
- IoT Edge feature
- Device Provisioning
- Get to Event-Hub Endpoint to process data
Cheers
azure azure-iot-hub azure-iot-edge azure-iot-central
azure azure-iot-hub azure-iot-edge azure-iot-central
asked May 16 '18 at 8:15
A MustaphaA Mustapha
41
41
add a comment |
add a comment |
3 Answers
3
active
oldest
votes
Azure IoT Central is a fully managed solution, you can't access underlying services including Azure IoT Hub. They are not exposed.
Reference "Compare Azure IoT Central and Azure IoT options".
What you can do is device connection. You can send device-to-cloud message and update device twin.
Reference "Device connectivity in Azure IoT Central".
Compare to Azure IoT Central, Azure IoT solution accelerators(original name: Azure IoT Suite) gives you more control of the underlying services. You have access to the underlying Azure services to manage them, or replace them as needed. For your use case, you can consider Azure IoT solution accelerators.
add a comment |
your requirement '3. Get to Event-Hub Endpoint to process data' can be done using your IoT Central App feature such as Continuous Data Export to the Event Hub.
The other way is to obtain an internal IoT Hub access to the events default endpoint from your IoT Central application access token like is shown here.
This approach allows to obtain an eventhubSasToken like is shown in the following code snippet:
"eventhubSasToken": {
"sasToken": "SharedAccessSignature sr=sb%3A%2F%2Fep-ns-saas-ep-15-262-xxxxxxxxxx.servicebus.windows.net%2Fep-ehub-saas-iothu-1044564-xxxxxxxxxx&sig=xxxxxx&se=1546197703&skn=service",
"entityPath": "ep-ehub-saas-iothu-1044564-xxxxxxxxxx",
"hostname": "sb://ep-ns-saas-ep-15-262-xxxxxxxxxx.servicebus.windows.net/"
}
Yes Roman you are right about Continuous Data Export which now exports data to your Event Hub in your own Azure Subscription. The second approach using the IoT Central access token with the IoT Hub APIs is not recommended as the access token format may change and thus this should not be taken as a dependency. The access token was intended for the IoT Central Explorer CLI only (docs.microsoft.com/en-us/azure/iot-central/…). We are currently working on an API for IoT Central to enable scenarios like this one.
– Vivian Liu - MSFT
Jan 3 at 23:38
add a comment |
IoT Edge is not supported in IoT Central. If you would like to request this feature, please add it to UserVoice and describe your use case.
Device Provisioning Service is supported in IoT Central. See https://docs.microsoft.com/en-us/azure/iot-central/concepts-connectivity
While there is no way to access the underlying services, you can export your data using Continuous Data Export to your own Event Hub endpoint in your own Azure subscription. From there you can process the data how you like.
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%2f50365638%2fstoring-data-azure-iot-central%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
Azure IoT Central is a fully managed solution, you can't access underlying services including Azure IoT Hub. They are not exposed.
Reference "Compare Azure IoT Central and Azure IoT options".
What you can do is device connection. You can send device-to-cloud message and update device twin.
Reference "Device connectivity in Azure IoT Central".
Compare to Azure IoT Central, Azure IoT solution accelerators(original name: Azure IoT Suite) gives you more control of the underlying services. You have access to the underlying Azure services to manage them, or replace them as needed. For your use case, you can consider Azure IoT solution accelerators.
add a comment |
Azure IoT Central is a fully managed solution, you can't access underlying services including Azure IoT Hub. They are not exposed.
Reference "Compare Azure IoT Central and Azure IoT options".
What you can do is device connection. You can send device-to-cloud message and update device twin.
Reference "Device connectivity in Azure IoT Central".
Compare to Azure IoT Central, Azure IoT solution accelerators(original name: Azure IoT Suite) gives you more control of the underlying services. You have access to the underlying Azure services to manage them, or replace them as needed. For your use case, you can consider Azure IoT solution accelerators.
add a comment |
Azure IoT Central is a fully managed solution, you can't access underlying services including Azure IoT Hub. They are not exposed.
Reference "Compare Azure IoT Central and Azure IoT options".
What you can do is device connection. You can send device-to-cloud message and update device twin.
Reference "Device connectivity in Azure IoT Central".
Compare to Azure IoT Central, Azure IoT solution accelerators(original name: Azure IoT Suite) gives you more control of the underlying services. You have access to the underlying Azure services to manage them, or replace them as needed. For your use case, you can consider Azure IoT solution accelerators.
Azure IoT Central is a fully managed solution, you can't access underlying services including Azure IoT Hub. They are not exposed.
Reference "Compare Azure IoT Central and Azure IoT options".
What you can do is device connection. You can send device-to-cloud message and update device twin.
Reference "Device connectivity in Azure IoT Central".
Compare to Azure IoT Central, Azure IoT solution accelerators(original name: Azure IoT Suite) gives you more control of the underlying services. You have access to the underlying Azure services to manage them, or replace them as needed. For your use case, you can consider Azure IoT solution accelerators.
answered May 17 '18 at 2:16
Rita Han - MSFTRita Han - MSFT
5,0811313
5,0811313
add a comment |
add a comment |
your requirement '3. Get to Event-Hub Endpoint to process data' can be done using your IoT Central App feature such as Continuous Data Export to the Event Hub.
The other way is to obtain an internal IoT Hub access to the events default endpoint from your IoT Central application access token like is shown here.
This approach allows to obtain an eventhubSasToken like is shown in the following code snippet:
"eventhubSasToken": {
"sasToken": "SharedAccessSignature sr=sb%3A%2F%2Fep-ns-saas-ep-15-262-xxxxxxxxxx.servicebus.windows.net%2Fep-ehub-saas-iothu-1044564-xxxxxxxxxx&sig=xxxxxx&se=1546197703&skn=service",
"entityPath": "ep-ehub-saas-iothu-1044564-xxxxxxxxxx",
"hostname": "sb://ep-ns-saas-ep-15-262-xxxxxxxxxx.servicebus.windows.net/"
}
Yes Roman you are right about Continuous Data Export which now exports data to your Event Hub in your own Azure Subscription. The second approach using the IoT Central access token with the IoT Hub APIs is not recommended as the access token format may change and thus this should not be taken as a dependency. The access token was intended for the IoT Central Explorer CLI only (docs.microsoft.com/en-us/azure/iot-central/…). We are currently working on an API for IoT Central to enable scenarios like this one.
– Vivian Liu - MSFT
Jan 3 at 23:38
add a comment |
your requirement '3. Get to Event-Hub Endpoint to process data' can be done using your IoT Central App feature such as Continuous Data Export to the Event Hub.
The other way is to obtain an internal IoT Hub access to the events default endpoint from your IoT Central application access token like is shown here.
This approach allows to obtain an eventhubSasToken like is shown in the following code snippet:
"eventhubSasToken": {
"sasToken": "SharedAccessSignature sr=sb%3A%2F%2Fep-ns-saas-ep-15-262-xxxxxxxxxx.servicebus.windows.net%2Fep-ehub-saas-iothu-1044564-xxxxxxxxxx&sig=xxxxxx&se=1546197703&skn=service",
"entityPath": "ep-ehub-saas-iothu-1044564-xxxxxxxxxx",
"hostname": "sb://ep-ns-saas-ep-15-262-xxxxxxxxxx.servicebus.windows.net/"
}
Yes Roman you are right about Continuous Data Export which now exports data to your Event Hub in your own Azure Subscription. The second approach using the IoT Central access token with the IoT Hub APIs is not recommended as the access token format may change and thus this should not be taken as a dependency. The access token was intended for the IoT Central Explorer CLI only (docs.microsoft.com/en-us/azure/iot-central/…). We are currently working on an API for IoT Central to enable scenarios like this one.
– Vivian Liu - MSFT
Jan 3 at 23:38
add a comment |
your requirement '3. Get to Event-Hub Endpoint to process data' can be done using your IoT Central App feature such as Continuous Data Export to the Event Hub.
The other way is to obtain an internal IoT Hub access to the events default endpoint from your IoT Central application access token like is shown here.
This approach allows to obtain an eventhubSasToken like is shown in the following code snippet:
"eventhubSasToken": {
"sasToken": "SharedAccessSignature sr=sb%3A%2F%2Fep-ns-saas-ep-15-262-xxxxxxxxxx.servicebus.windows.net%2Fep-ehub-saas-iothu-1044564-xxxxxxxxxx&sig=xxxxxx&se=1546197703&skn=service",
"entityPath": "ep-ehub-saas-iothu-1044564-xxxxxxxxxx",
"hostname": "sb://ep-ns-saas-ep-15-262-xxxxxxxxxx.servicebus.windows.net/"
}
your requirement '3. Get to Event-Hub Endpoint to process data' can be done using your IoT Central App feature such as Continuous Data Export to the Event Hub.
The other way is to obtain an internal IoT Hub access to the events default endpoint from your IoT Central application access token like is shown here.
This approach allows to obtain an eventhubSasToken like is shown in the following code snippet:
"eventhubSasToken": {
"sasToken": "SharedAccessSignature sr=sb%3A%2F%2Fep-ns-saas-ep-15-262-xxxxxxxxxx.servicebus.windows.net%2Fep-ehub-saas-iothu-1044564-xxxxxxxxxx&sig=xxxxxx&se=1546197703&skn=service",
"entityPath": "ep-ehub-saas-iothu-1044564-xxxxxxxxxx",
"hostname": "sb://ep-ns-saas-ep-15-262-xxxxxxxxxx.servicebus.windows.net/"
}
answered Jan 1 at 13:09
Roman KissRoman Kiss
2,240128
2,240128
Yes Roman you are right about Continuous Data Export which now exports data to your Event Hub in your own Azure Subscription. The second approach using the IoT Central access token with the IoT Hub APIs is not recommended as the access token format may change and thus this should not be taken as a dependency. The access token was intended for the IoT Central Explorer CLI only (docs.microsoft.com/en-us/azure/iot-central/…). We are currently working on an API for IoT Central to enable scenarios like this one.
– Vivian Liu - MSFT
Jan 3 at 23:38
add a comment |
Yes Roman you are right about Continuous Data Export which now exports data to your Event Hub in your own Azure Subscription. The second approach using the IoT Central access token with the IoT Hub APIs is not recommended as the access token format may change and thus this should not be taken as a dependency. The access token was intended for the IoT Central Explorer CLI only (docs.microsoft.com/en-us/azure/iot-central/…). We are currently working on an API for IoT Central to enable scenarios like this one.
– Vivian Liu - MSFT
Jan 3 at 23:38
Yes Roman you are right about Continuous Data Export which now exports data to your Event Hub in your own Azure Subscription. The second approach using the IoT Central access token with the IoT Hub APIs is not recommended as the access token format may change and thus this should not be taken as a dependency. The access token was intended for the IoT Central Explorer CLI only (docs.microsoft.com/en-us/azure/iot-central/…). We are currently working on an API for IoT Central to enable scenarios like this one.
– Vivian Liu - MSFT
Jan 3 at 23:38
Yes Roman you are right about Continuous Data Export which now exports data to your Event Hub in your own Azure Subscription. The second approach using the IoT Central access token with the IoT Hub APIs is not recommended as the access token format may change and thus this should not be taken as a dependency. The access token was intended for the IoT Central Explorer CLI only (docs.microsoft.com/en-us/azure/iot-central/…). We are currently working on an API for IoT Central to enable scenarios like this one.
– Vivian Liu - MSFT
Jan 3 at 23:38
add a comment |
IoT Edge is not supported in IoT Central. If you would like to request this feature, please add it to UserVoice and describe your use case.
Device Provisioning Service is supported in IoT Central. See https://docs.microsoft.com/en-us/azure/iot-central/concepts-connectivity
While there is no way to access the underlying services, you can export your data using Continuous Data Export to your own Event Hub endpoint in your own Azure subscription. From there you can process the data how you like.
add a comment |
IoT Edge is not supported in IoT Central. If you would like to request this feature, please add it to UserVoice and describe your use case.
Device Provisioning Service is supported in IoT Central. See https://docs.microsoft.com/en-us/azure/iot-central/concepts-connectivity
While there is no way to access the underlying services, you can export your data using Continuous Data Export to your own Event Hub endpoint in your own Azure subscription. From there you can process the data how you like.
add a comment |
IoT Edge is not supported in IoT Central. If you would like to request this feature, please add it to UserVoice and describe your use case.
Device Provisioning Service is supported in IoT Central. See https://docs.microsoft.com/en-us/azure/iot-central/concepts-connectivity
While there is no way to access the underlying services, you can export your data using Continuous Data Export to your own Event Hub endpoint in your own Azure subscription. From there you can process the data how you like.
IoT Edge is not supported in IoT Central. If you would like to request this feature, please add it to UserVoice and describe your use case.
Device Provisioning Service is supported in IoT Central. See https://docs.microsoft.com/en-us/azure/iot-central/concepts-connectivity
While there is no way to access the underlying services, you can export your data using Continuous Data Export to your own Event Hub endpoint in your own Azure subscription. From there you can process the data how you like.
answered Jan 3 at 23:45
Vivian Liu - MSFTVivian Liu - MSFT
221210
221210
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%2f50365638%2fstoring-data-azure-iot-central%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