Azure Sphere MT3620 Insights – November 2021

by Contributed | Nov 12, 2021 | Technology

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

As the season of Fall begins to color the leaves of northern hemisphere locales such as Microsoft’s headquarters in Redmond, it brings with it the joy of connecting with loved ones through seasonal holidays and connecting with the transient beauty of nature preparing for cold, dark winter. This is also a time for Azure Sphere to focus on a different sort of connectivity. This month’s OS update paves the way for Azure Sphere to be connected in more relevant environments than ever.

Azure Sphere now supports web proxy. We’re really excited about this because it’s so helpful for so many customer applications. Azure Sphere was designed to provide end-to-end encrypted dataflow, but I’ve been asked what does this do for network security? Does it help participate in the policies and analysis of network traffic to detect and thwart malicious network intruders? With web proxy, Azure Sphere devices can now engage with enterprise network security systems, policies, tools and procedures!

Another item of interest is that Azure Sphere has laid the foundations for improving MQTT support across multiple clouds. Hybrid cloud solutions are more relevant now than ever, and Azure Sphere was designed to support connectivity for anything you may want to securely connect to. One of the best benefits of Azure Sphere is its Microsoft managed identity, backed by our Azure Sphere Security Service. This service provides a certificate that proves that the device is authentic, rooted in hardware trust, and has been forced to attest its configuration. This certificate, by default, is used as a client TLS certificate to connect to any Azure service. We’re paving the way to make this certificate even more useful for connecting to other cloud services so you can trust the device’s identity and easily connect as needed. We hope to put out additional documentation around how to solve these problems, so stay tuned for more!

Whatever season you may be experiencing this month, we wish you the best—and many connections both digital and human!

#M365GovCommunityCall November 2021: Teach a Govie to Fish (through MSFT updates)

by Contributed | Nov 9, 2021 | Technology

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

https://www.youtube-nocookie.com/embed/hsNc_QjYwfw

At the beginning of November, Microsoft had their second Ignite of the year, announcing or further clarifying details around many of the latest and near-immediate future features expected to rollout to Microsoft 365. However, as many of the US Federal cloud tenants see features months (if not longer) after they hit the commercial tenant, these users are often left wondering “what’s next for us” instead of having the same excitement commercial tenant owners have coming out of these conferences.

In this episode, we meet with Microsoft architect John Moh (LinkedIn) to discuss our favorite ways to stay up to date on what’s available to us in the GCC, GCC-H, and DOD tenants!

Government Community Events

• November 11: SharePoint User Group of DC – MS Ignite 2021 Highlights


• November 16: Power BI of DC – Monthly Meetup – Topic TBD


• November 17: Washington DC Power Platform User Group – Intro to AI


• December 2: NARA Microsoft 365 User Group – Monthly Meeting – Topic TBD (Government Only)


• December 2: Microsoft Webinar – Dive into your CMMC Compliance Journey


• December 8: Azure Government Meetup – Monthly Meetup – Topic TBD


• December 14-16: IN PERSON 365 EduCon DC (by SharePoint Fest)

In the News

• Azure Security Benchmark Workbook


• Azure Sentinel Threat Intelligence Workbook


• CMMC 2.0 Release – Summit 7’s update summary


• Mesh for Microsoft Teams

Roadmap Update

• Together Mode (GCC-H)


• Live Transcription for Teams Meetings (GCC-H)


• Presenter Mode in Desktop/Window Sharing (GCC-H & DOD)


• Breakout Rooms Pre-Meeting Room Creation

Today’s Discussion

• Microsoft’s New Roadmap


• Azure Products by Region


• Microsoft Defender for Gov

Get started with minimal API for .NET 6

by Contributed | Nov 8, 2021 | Technology

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

TLDR; Using minimal API, you can create a Web API in just 4 lines of code by leveraging new features like top-level statements and more.

 Why Minimal API

There are many reasons for wanting to create an API in a few lines of code:

• Create a prototype. Sometimes you want a quick result, a prototype, something to discuss with your colleagues. Having something up and running quickly enables you to quickly do changes to it until you get what you want.


• Progressive enhancement. You might not want all the “bells and whistles” to start with but you may need them over time. Minimal API makes it easy to gradually add what you need, when you need it.

How is it different from a normal Web API?

There are a few differences:

• Less files. Startup.cs isn’t there anymore, only Program.cs remains.


• Top level statements and implicit global usings. Because it’s using top level statements, using and namespace are gone as well, so this code:

 using System;
   namespace Application
   {
        class Program
        {
            static void Main(string[] args)
            {
                Console.WriteLine("Hello World!");
            }
        }
   }

is now this code:

 Console.WriteLine("Hello World!");

• Routes Your routes aren’t mapped to controller classes but rather setup with a Map[VERB] function, like you see above with MapGet() which takes a route and a function to invoke when said route is hit.

 Your first API

To get started with minimal API, you need to make sure that .NET 6 is installed and then you can scaffold an API via the command line, like so:

dotnet new web -o MyApi -f net6.0

Once you run that, you get a folder MyApi with your API in it.

What you get is the following code in Program.cs:

var builder = WebApplication.CreateBuilder(args);
var app = builder.Build();

if (app.Environment.IsDevelopment())
{
    app.UseDeveloperExceptionPage();
}

app.MapGet("/", () => "Hello World!");

app.Run();

To run it, type dotnet run. A little difference here with the port is that it assumes random ports in a range rather than 5000/5001 that you may be used to. You can however configure the ports as needed. Learn more on this docs page

 Explaining the parts

Ok so you have a minimal API, what’s going on with the code?

 Creating a builder

var builder = WebApplication.CreateBuilder(args);

On the first line you create a builder instance. builder has a Services property on it, so you can add capabilities on it like Swagger Cors, Entity Framework and more. Here’s an example where you set up Swagger capabilities (this needs install of the Swashbuckle NuGet to work though):

builder.Services.AddEndpointsApiExplorer();
builder.Services.AddSwaggerGen(c =>
    {
        c.SwaggerDoc("v1", new OpenApiInfo { Title = "Todo API", Description = "Keep track of your tasks", Version = "v1" });
    });

Creating the app instance

Here’s the next line:

var app = builder.Build();

Here we create an app instance. Via the app instance, we can do things like:

• Starting the app, app.Run()


• Configuring routes, app.MapGet()


• Configure middleware, app.UseSwagger()

Defining the routes

With the following code, a route and route handler is configured:

app.MapGet("/", () => "Hello World!");

The method MapGet() sets up a new route and takes the route “/” and a route handler, a function as the second argument () => “Hello World!”.

Starting the app

To start the app, and have it serve requests, the last thing you do is call Run() on the app instance like so:

app.Run();

 Add routes

To add an additional route, we can type like so:

public record Pizza(int Id, string Name); 
app.MapGet("/pizza", () => new Pizza(1, "Margherita"));

Now you have code that looks like so:

var builder = WebApplication.CreateBuilder(args);
var app = builder.Build();

if (app.Environment.IsDevelopment())
{
    app.UseDeveloperExceptionPage();
}

app.MapGet("/pizza", () => new Pizza(1, "Margherita"));
app.MapGet("/", () => "Hello World!");

public record Pizza(int Id, string Name); 

app.Run();

Where you to run this code, with dotnet run and navigate to /pizza you would get a JSON response:

{
  "pizza" : {
    "id" : 1,
    "name" : "Margherita"
  }
}

Example app

Let’s take all our learnings so far and put that into an app that supports GET and POST and lets also show easily you can use query parameters:

var builder = WebApplication.CreateBuilder(args);
var app = builder.Build();

if (app.Environment.IsDevelopment())
{
    app.UseDeveloperExceptionPage();
}

var pizzas = new List<Pizza>(){
   new Pizza(1, "Margherita"),
   new Pizza(2, "Al Tonno"),
   new Pizza(3, "Pineapple"),
   new Pizza(4, "Meat meat meat")
};

app.MapGet("/", () => "Hello World!");
app.MapGet("/pizzas/{id}", (int id) => pizzas.SingleOrDefault(pizzas => pizzas.Id == id));
app.MapGet("/pizzas", (int ? page, int ? pageSize) => {
    if(page.HasValue && pageSize.HasValue) 
    {
        return pizzas.Skip((page.Value -1) * pageSize.Value).Take(pageSize.Value);
    } else {
        return pizzas;
    }
});
app.MapPost("/pizza", (Pizza pizza) => pizzas.Add(pizza));

app.Run();

public record Pizza(int Id, string Name);

Run this app with dotnet run

In your browser, try various things like:

• “http://localhost:{PORT}/pizzas“, should give you all pizzas back


• “http://localhost:{PORT}/pizzas?page=1&pageSize=2“, should give you the two first pizzas. See how the query parameters are working for you.


• “http://localhost:{PORT}/pizzas/2“, should give you the “Al Tonno” pizza back. Here you have the {id} matching the 2 and thereby it filters down on the one item that matches.

 Learn more

Check out these LEARN modules on learning to use minimal API

• Your first minimal API + Swagger


• minimal API with Entity Framework


• minimal API with React