Mandatory Check, Update and Validate of Hardware Dev Center (HDC) Profile

by Contributed | Jun 22, 2021 | Technology

This article is contributed. See the original author and article here.

We are currently performing updates to the Hardware Dev Center (HDC).  As part of this effort, it is vital that you update/complete your HDC Profile to keep your account active. To keep your HDC account active, you must update/complete your HDC profile by July 2, 2021. Please ensure that the following information is up to date:

• Business name


• Address


• Contact phone


• Email

Even if there are no changes to this information, you must validate the profile settings in HDC to maintain your program access. Remember that HDC access is needed to submit drivers, devices and systems for signing or certification.

To update your HDC Partner Profile:

• Log in to the Microsoft Partner Center Dashboard using the AAD Global Admin account (or account with Global Admin AAD Role assigned).  

• Link to Dashboard (https://partner.microsoft.com/en-us/dashboard/home) 

• Click on the “Gear” Icon in the upper right-hand corner of the screen.  

• Then click on “Account Settings”. 

• Click “Organization Profile”, and then click on “Legal”. 

• On the “Legal info” page you will see two tabs, Partner and Developer.

• Click the “Partner” tab and ensure that the information under “Legal business profile” is complete, and correct. If any fields are blank, or any information needs to be updated.

• Click “Developer”. 

• Under “Contact info”, ensure that all fields are completed with accurate contact information for the person in your organization that is responsible for your Partner Center registration. 

• If you are unable to update your profile information, please open a ticket with Partner Center support. 

• Click on the “Support” button. Under “Problem summary” enter “Can’t update partner profile”. Under “Problem type” select “General > Accounts, Onboarding, Access > Company details (legal business profile)” 

Thank you for your help in maintaining the Hardware Dev Center! We appreciate your prompt attention to this matter.

Adding Context to IoT Data Just Became Easier

by Contributed | Jun 22, 2021 | Technology

This article is contributed. See the original author and article here.

The growing number of devices connecting to the cloud is producing treasure troves of information. This information can be used to not only understand the state of a device, but the state of an entire environment such as a building, energy grid, or factory. However, this vast amount of data can produce its own challenges. As each device generates a time series stream that is often labeled with an encoded tag, it can be hard to understand how different streams are related, or how an overall environment is behaving.

This is where Azure Digital Twins comes in. Azure Digital Twins enables you to create digital models of assets, places, people, and processes, and then relate these items based on their real-world relationships. Now, you can use the Azure Digital Twins plugin for Azure Data Explorer to combine the digital models of your environment with time series data from your devices. More specifically, you can use the plugin to contextualize disparate time series data in ADX by reasoning across digital twins and their relationships to gain insights into the behavior of your modeled environments over time.

For example, with the new Azure Digital Twins plugin for ADX, you can write a query that…

1. selects digital twins of interest via the Azure Digital Twins query plugin, then


2. joins those twins against the respective times series data in ADX, and then


3. performs advanced time series analytics on those twins.

To get you up and running with the new plugin, we’ve created an example scenario where you will combine data in a sample twin graph in Azure Digital Twins with sample time series data in ADX. More specifically, you’ll use joint Azure Digital Twins/ADX queries to understand the operational behavior of various portions of a power distribution grid.

Create a twin graph of an energy grid using Azure Digital Twins Explorer

1. To get started, create an Azure Digital Twins instance using the CLI commands below or via the Azure portal. Copy the instance’s URL once it is online.

az account set --subscription <your-subscription-ID> az dt create -n <instance-name> -g <resource-group>

     Note: Ensure the resource group exists.  

2. Grant yourself the Azure Digital Twins Data Owner role on the instance. It may take up to five minutes for this RBAC change to apply. 

az dt role-assignment create -n <instance-name> --assignee "<owneruser@microsoft.com>" --role "Azure Digital Twins Data Owner"

2. Download the sample models and graph from the energy-grid-example folder to your local computer. You can do this by cloning this repository or downloading it as a ZIP, and then navigating to the energy-grid-example folder on your machine.


3. Open Azure Digital Twins Explorer. It should prompt you to enter your Azure Digital Twins instance URL. If not, click on the globe icon in the top right corner.


4. Enter your Azure Digital Twins instance URL (endpoint must start with ‘https://’).


5. On the left pane, click on the Upload a Model button (cloud icon with upward arrow).

           i. Go to the folder where you downloaded the repository. Navigate into /model/energy-grid-example.

           ii. Select all the JSON files (models) and upload them.

7. In the middle pane, click the Import Graph button (also a cloud icon with upward arrow).

             i. Within /model/energy-grid-example, select distributionGrid.xlsx to import it.

8. You should see a graph preview. Click on the floppy disk icon to finish importing the graph (this creates twins and relationships).


9. Navigate back to the Twin Graph tab. In the query section, type in “SELECT * FROM DIGITALTWINS” and select Run Query. You should see the graph displayed in the Twin Graph window.


10. Click on one of the leaf nodes that has this model: dtmi:example:grid:plants:domesticConsumer;1.


11. Update the PowerRequirement value to 500 and save it (using the disc button circled in red below) to patch the twin.

Run joint Azure Digital Twins/ADX queries to understand the behavior of the energy grid

1. Connect to the Samples database on the public ADX help cluster. The database features the table SamplePowerRequirementHistorizedData that contains historized property values over a one month period for selected digital twins in the energy grid.


2. Get the list of example queries in the sample-queries. Kusto file. Copy and paste each query into ADX. To run a query, click on the query to highlight it and press the Run button. In each query, replace <your_ADT_endpoint> with your instance’s endpoint. Your endpoint should be in quotes, start with https://, and be followed by a semicolon. For example:

let ADTendpoint = "https://MyExampleADTinstance.api.wcus.digitaltwins.azure.net";

3. Run the below query, which will invoke the plugin and return all twins in the energy grid.

//Get all twins in your Azure Digital Twins instance
let ADTendpoint = <your_ADT_endpoint>;
let ADTquery = "SELECT T FROM DIGITALTWINS T";
evaluate azure_digital_twins_query_request(ADTendpoint, ADTquery)

4. Now that you’ve use the plugin to run an Azure Digital Twins query from ADX, run the next query to retrieve the IDs of the digital twins that are fed power by the Fall Street Substation. The Azure Digital Twins plugin query selects these twins based on those that have a ‘feeds’ relationship with that substation.

// Get the twin ID of all consumers fed by the Fall Street substation
let ADTendpoint = <your_ADT_endpoint>;
let ADTquery = "SELECT CSMR.$dtId as tid FROM DIGITALTWINS SUB JOIN CSMR RELATED SUB.feeds WHERE SUB.$dtId = 'sub_fall_street' AND IS_PRIMITIVE(CSMR.$dtId)";
evaluate azure_digital_twins_query_request(ADTendpoint, ADTquery)

5. Now that you have selected the twins of interest from your twin-graph, you can join the twin IDs against the respective time series in ADX and perform time-series analytics. For example, the below query calculates the average power usage on an hourly basis for all customers fed by the Fall Street substation during week 10.

// Chart the average hourly power usage of consumers fed by the Fall Street substation ('sub_fall_street') during week 10
let ADTendpoint = <your_ADT_endpoint>;
let ADTquery = "SELECT CSMR.$dtId as tid FROM DIGITALTWINS SUB JOIN CSMR RELATED SUB.feeds WHERE SUB.$dtId = 'sub_fall_street' AND IS_PRIMITIVE(CSMR.$dtId)";
let weekNumber = 10;
let startDate = datetime_add('week',weekNumber - 1, make_datetime(2021,1,1));
let endDate = datetime_add('week',1, startDate);
evaluate azure_digital_twins_query_request(ADTendpoint, ADTquery)
| extend twinId = tostring(tid)
| join kind=inner (SamplePowerRequirementHistorizedData) on twinId
| project timestamp, twinId, value
| where timestamp between (startDate .. endDate)
| summarize avg(value) by bin(timestamp,1h),twinId
| render timechart

6. This last example selects the twins that feed power into the solar grid, identifies missing time series samples, fills in the missing samples with interpolated data points, and then identifies anomalies in the time series for each twin.

// Identify any anomalies in the data
let ADTendpoint = <your_ADT_endpoint>;
let ADTquery = "SELECT PLANT.$dtId as tid FROM DIGITALTWINS PLANT JOIN GRID RELATED PLANT.feeds WHERE GRID.$dtId = 'pl_solar_gen' AND IS_PRIMITIVE(PLANT.$dtId)";
let weekNumber = 10;
let startDate = datetime_add('week',weekNumber - 1, make_datetime(2021,1,1));
let endDate = datetime_add('week',1, startDate);
evaluate azure_digital_twins_query_request(ADTendpoint, ADTquery)
| extend twinId = tostring(tid)
| join kind=inner (SamplePowerRequirementHistorizedData) on twinId
| project timestamp, twinId, value
| where timestamp between (startDate .. endDate)
| make-series AvgPower=avg(value) on timestamp step 10m by twinId
| extend NoGapsTemp=series_fill_linear(AvgPower)
| project timestamp, NoGapsTemp, twinId
| extend anomalies = series_decompose_anomalies(NoGapsTemp,4)
| render anomalychart with(anomalycolumns=anomalies)

7. Want even more fun? Build an ADX dashboard with charts from your new Azure Digital Twins/ADX queries! ADX also offers integrations with third party visualization packages such as Power BI, Grafana, Tableau and others.

Step 3: Delete all resources

When you’re finished, follow these steps to delete the resources used in this walkthrough.

1. Delete your Azure Digital Twins instance using the following CLI command. This will also delete the twins and models associated with the instance.

az dt delete -n <instance-name>

2. Remove the cloned or downloaded repository from your machine.

For more information

• Read more about the plugin in 


• Check out the above example and others on GitHub