The September 11th Weekly Roundup is Posted!

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

 

News this week includes:

 

Microsoft Ignite preparation is in full swing, with several resources on how what to expect from Microsoft Search, Yammer, Humans of IT and more.

 

Microsoft Endpoint Manager announces support for Surface Duo devices

 

Azure Sphere OS update 20.09 now available for compatibility testing

 

@Victor Ivanidze  is our Member of the Week, and a great contributor in the Office 365 community. 

 

View the Weekly Roundup for Sept 7-11th in Sway and attached PDF document.

 

Microsoft Flow 101: Getting Started in Power Automate as an Educator or Administrator

Microsoft Flow 101: Getting Started in Power Automate as an Educator or Administrator

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

This article was written by Gabi Stein from Microsoft’s EDU Engagement Team. Gabi is a Program Manager for Modern Learning Experiences.

 

Power Automate is one of Microsoft’s best kept secrets, but it’s time for all to know the power of this amazing toolPower Automate can be broken down into three main pieces: connectors, flows, and power apps.  

 

Connectors: Are the application actions that you want to put together to make your life easier.  

Flows: Are the actual pieces being put together, so two or more connectors = one flow  

PowerApps: Power apps bring everything together and combine with the user interface (UI) to create a custom app that you can add to your Team.  

 

Take a look at some of the examples below to get ideas for just a few of the innovative ways you can leverage Power Automate! 

 

Tracking health in Teams Posts: 

Health tracking can be used among high school teachers, higher ed teachers, and higher ed students to view what types of messages are being sent in your team’s channels. When a new message is posted, have it sent to an excel sheet to build custom reports such as: Seeing what channels have the most messages or building word clouds to surface common themes in your data. In addition, you can add the HTML to text connector to remove HTML tags from your analysis.  

 

image001.png

 

Get updates from the data you have in Power BI  

If you have important data in Power BI, but don’t always remember to check, you can have the data come to you with this simple flow! You can combine the available Power BI alert functions to automatically post an Adaptive Card as a reminder to yourself or send a message to a specific channel. Check out this helpful article for setting up data alerts in Power BI: https://docs.microsoft.com/en-us/power-bi/create-reports/service-set-data-alerts 

 

image002.png

 

Send lost email to yourself in Teams:

As an educator or administrator, it’s easy to get overwhelmed with emails and manage all the messages that need attention in Teams and Outlook. Using Power Automate, you can have emails sent by parents go to a specific folder and simultaneously send yourself a reminder message in Teams to remember to chech those messages later. This is just one of many use cases for this handy app.

 

image003.png

 

Daily Reminder Emails/Teams Notes

Do you have any daily tasks that you need to remind yourself about? Use Power Automate to send yourself a message in Teams, email or both! A lot of educators use this feature to remember to view the previous day’s data, but it can be used for any reminder you can think of!

 

image004.png

 

In addition to the flows mentioned here, checkout what Power Automate has in their education templates: https://us.flow.microsoft.com/en-us/collections/education/. If you have ideas for flows you would like to build or need assistance putting one together, please let our team know. We would love to collaborate with you! Just send me an email and we will get back to you right away. 

 

ADF Data Flows Sneak Peek: Expression Builder UX Updates

ADF Data Flows Sneak Peek: Expression Builder UX Updates

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

ADF Data Flows Expression Builder is getting some new enhancements next week. Here’s a sneak peek at some of what’s coming!

 

expbuildernew1.png

 

Join @daperlov and @Mark Kromer next week for our YouTube Live Stream where we’ll walk through these updates in detail.

 

  • New “Locals” feature where you can now define a variable that is scoped to your current transformation allowing you to reuse logic that used to require you to copy that formula multiple times inside your expressions. Another current technique is to use Derived Columns to generate synthetic columns that were not meant for loading into your destination and were used in this “temporary” way. Now you can use locals to store data that won’t propagate outside of the current scope.
 
 
  • Now you can edit directly inside Derived Column transformation text boxes without the Expression Builder automatically launching. Typing or editing your formulas directly will also include standard validation and enables copy & paste without needing to open the Expression Builder. This means that the Clone button has moved to the top of the column list as well as a new Open Expression Builder option.

derivedcolnew1.png

  • We are closing in on our 1-year anniversary of the GA of Data Flows in ADF and we gathered a ton of feedback from our community that we consolidated into these updates including making the experience full-screen and adding inline function help. We hope that you will find these changes make for a more productive and enjoyable experience in ADF data flows as we’ve recognized that the bulk of time spent in ADF by our data flow ETL developers ends up being inside the Expression Builder.
ANCM not reading “ASPNETCORE_ENVIRONMENT” variable from local environment.

ANCM not reading “ASPNETCORE_ENVIRONMENT” variable from local environment.

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

After upgrading the asp.net core application to asp.net core 3.1 version, application is not able to read the “ASPNETCORE_ENVIRONMENT” variable from local environment and getting defaulted to web.config values.

 

ASPNETCORE_ENVIRONMENT value is set as Development in Web.config.

 

Ramchandra_Kudtarkar_0-1599855254632.png

 

 

ASPNETCORE_ENVIRONMENT value is set as Production in local environment of Azure App Service application setting.

 

Ramchandra_Kudtarkar_1-1599855254635.png

 

 

ANCM is Preferring value set in Web.config over the local environment variable in Azure App service application setting.

 

Ramchandra_Kudtarkar_2-1599855254638.png

 

 

Solution:

 

We need to add a switch “ANCM_PREFER_ENVIRONMENT_VARIABLES” and set as “true”  to allow ANCM to prefer the local environment over the Web.config values. Below is the screenshot of app service app settings.

 

Ramchandra_Kudtarkar_3-1599855254640.png

 

If the switch is added in both Web.config and local environment and both of them are set to “true” then web.config “ASPNETCORE_ENVIRONMENT” will take precedence.

 

After setting “ANCM_PREFER_ENVIRONMENT_VARIABLES” as “true” in App service App settings, ANCM is preferring the local environment variable “ASPNETCORE_ENVIRONMENT” which is set to production .

 

Ramchandra_Kudtarkar_4-1599855254642.png

 

For more information about these changes, please refer below Github issues.

https://github.com/dotnet/aspnetcore/pull/20006

https://github.com/dotnet/aspnetcore/issues/19450

Azure IoT TLS: Changes are coming! (…and why you should care)

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

Microsoft is updating Azure services in a phased manner to use TLS certificates from a different set of Certificate Authorities (CAs) beginning August 13, 2020 and concluding approximately on October 26, 2020. We expect that most Azure IoT customers will not be impacted; however, your application may be impacted if you explicitly specify a list of acceptable CAs (a practice known as “certificate pinning”). This change is limited to services in public Azure cloud and no sovereign cloud like Azure China.

 

This change is being made because the current CA certificates do not comply with one of the CA/Browser Forum Baseline requirements. This was reported on July 1, 2020 and impacts multiple popular Public Key Infrastructure (PKI) providers worldwide. Today, most of the TLS certificates used by Azure services are issued from the “Baltimore CyberTrust Root” PKI.

The following services used by Azure IoT devices will remain chained to the Baltimore CyberTrust Root*, but their TLS server certificates will be issued by new Intermediate Certificate Authorities (ICAs) starting October 5, 2020:

  1. Azure IoT Hub
  2. Azure IoT Hub Device Provisioning Service (DPS)
  3. Azure Storage Services

 

If any client application or device has pinned to an Intermediate CA or leaf certificate rather than the Baltimore CyberTrust Root, immediate action is required to prevent disruption of IoT device connectivity to Azure.

 

* Other Azure service TLS certificates may be issued by a different PKI.

 

Certificate Renewal Summary

The table below provides information about the certificates that are being rolled. Depending on which certificate your device or gateway clients use for establishing TLS connections, action may be needed to prevent loss of connectivity.

 

Certificate

Current

Post Rollover (Oct 5, 2020)

Action

Root

Thumbprint: d4de20d05e66fc53fe1a50882c78db2852cae474
Expiration: Monday, May 12, 2025, 4:59:00 PM
Subject Name:
CN = Baltimore CyberTrust Root

OU = CyberTrust
O = Baltimore
C = IE

 

 

 

Not Changing

None

Intermediates

Thumbprints:

 

CN = Microsoft IT TLS CA 1

Thumbprint: 417e225037fbfaa4f95761d5ae729e1aea7e3a42

—————————————————-

CN = Microsoft IT TLS CA 2

Thumbprint: 54d9d20239080c32316ed9ff980a48988f4adf2d

—————————————————-

CN = Microsoft IT TLS CA 4

Thumbprint: 8a38755d0996823fe8fa3116a277ce446eac4e99

—————————————————-

CN = Microsoft IT TLS CA 5

Thumbprint: Ad898ac73df333eb60ac1f5fc6c4b2219ddb79b7

—————————————————-

 

Expiration: ‎Friday, ‎May ‎20, ‎2016 5:52:38 AM
Subject Name:

OU = Microsoft IT

O = Microsoft Corporation

L = Redmond

S = Washington

C = US

Thumbprints:

 

CN = Microsoft RSA TLS CA 01

Thumbprint: 417e225037fbfaa4f95761d5ae729e1aea7e3a42

—————————————————-

CN = Microsoft RSA TLS CA 02

Thumbprint: b0c2d2d13cdd56cdaa6ab6e2c04440be4a429c75

—————————————————-

 

Expiration: ‎Tuesday, ‎October ‎8, ‎2024 12:00:00 AM;
Subject Name:

O = Microsoft Corporation

C = US

Required

Leaf (IoT Hub)
 

Thumbprint: 8b1a359705188c5577cb2dcd9a06331807c0bb97
Expiration: ‎Friday, ‎March ‎19, ‎2021 6:15:48 PM

Subject Name:

CN = *.azure-devices.net

Thumbprint: Coming soon
Expiration: Coming soon
Subject Name:
CN = *.azure-devices.net

Required

Leaf (DPS)
 

Thumbprint: f568f692f3274ecbb479c94272d6f3344a3f0247
Expiration: ‎Friday, ‎March ‎19, ‎2021 5:58:35 PM

Subject Name:

CN = *.azure-devices-provisioning.net

Thumbprint: Coming soon
Expiration: Coming soon
Subject Name:
CN = *.azure-devices-provisioning.net

Required

Note: Both the intermediate and lea certificates are expected to change frequently. We recommend not taking dependencies on them and instead pinning the root certificate as it rolls less frequently.

 

 

Action Required

  1. If your devices depend on the operating system certificate store for getting these roots or use the device/gateway SDKs as provided, then no action is required.
  2. If your devices pin the Baltimore root CA among others, then no action is required related to this change.
    1. If your device interacts with other Azure services (e.g. IoT Edge -> Microsoft Container Registry), then you must pin additional roots as provided here.
  3. If your devices use a connection stack other than the ones provided in an Azure IoT SDK, and pin any intermediary or leaf TLS certificates instead of the Baltimore root CA, then immediate action is required:
    1. To continue without disruption due to this change, Microsoft recommends that client applications or devices pin the Baltimore root –
      1. Baltimore Root CA
        (Thumbprint: d4de20d05e66fc53fe1a50882c78db2852cae474)
      2. To prevent future disruption, client applications or devices should also pin the following roots:
        1. Microsoft RSA Root Certificate Authority 2017
          (Thumbprint: 73a5e64a3bff8316ff0edccc618a906e4eae4d74)
        2. Digicert Global Root G2
          (Thumbprint: df3c24f9bfd666761b268073fe06d1cc8d4f82a4)
    2. To continue pinning intermediaries, replace the existing certificates with the new intermediates CAs:
      1. Microsoft RSA TLS CA 01
        (Thumbprint: 703d7a8f0ebf55aaa59f98eaf4a206004eb2516a)
      2. Microsoft RSA TLS CA 02
        (Thumbprint: b0c2d2d13cdd56cdaa6ab6e2c04440be4a429c75)
      3. To minimize future code changes, also pin the following ICAs:
        1. Microsoft Azure TLS Issuing CA 01
          (Thumbprint: 2f2877c5d778c31e0f29c7e371df5471bd673173)
        2. Microsoft Azure TLS Issuing CA 02
          (Thumbprint: e7eea674ca718e3befd90858e09f8372ad0ae2aa)
        3. Microsoft Azure TLS Issuing CA 05
          (Thumbprint: 6c3af02e7f269aa73afd0eff2a88a4a1f04ed1e5)
        4. Microsoft Azure TLS Issuing CA 06
          (Thumbprint: 30e01761ab97e59a06b41ef20af6f2de7ef4f7b0)
  1. If your client applications, devices, or networking infrastructure (e.g. firewalls) perform any sub root validation in code, immediate action is required:
    1. If you have hard coded properties like Issuer, Subject Name, Alternative DNS, or Thumbprint of any certificate other than the Baltimore Root CA, then you will need to modify this to reflect the properties of the newly pinned certificates.
    2. Note: This extra validation, if done, should cover all the pinned certificates to prevent future disruptions in connectivity.

 

Validation

We recommend performing some basic validation to mitigate any unintentional impact to your IoT infrastructure connecting to Azure IoT Hub and DPS. We will be providing a test environment for your convenience to try out before we roll these certificates in production environments. The connection strings for this test environment will be updated here soon.

 

A successful TLS connection to the test environment indicates a positive test outcome – that your infrastructure will work as is with these changes. The test connection strings contain invalid keys, so once the TLS connection has been established, any run time operations performed against these services will fail. This is by design since these resources exist solely for customers to validate their TLS connectivity. The test environment will be available until all public cloud regions have been updated.

 

Support

If you have any technical questions on implementing these changes, with the options below and a member from our engineering team will get back to you shortly.

  • Issue Type: Technical
  • Service: Internet of Things/IoT SDKs
  • Problem type: Connectivity
  • Problem subtype: Unable to connect

 

Additional Information

  1. IoT Show: To know more about TLS certificates and PKI changes related to Azure IoT, please check out the IoT Show:

  2. Microsoft wide communications: To broadly notify customers, Microsoft had sent a Service Health portal notification on Aug 3rd, 2020 and released a public document that include timelines, actions that need to be taken, and details regarding the upcoming changes to our Public Key Infrastructure (PKI).