In previous articles, we have covered various basic aspects of Blazor WebAssembly application. In this article, we are going to demonstrate how the Blazor WebAssembly app can be deployed in an Azure App Service. What are various options for deploying Blazor Apps ? There are two different types of Blazor applications – Blazor Server Apps…Deploying a Blazor WebAssembly App to Azure App Service — The Code Blogger
In this episode of Azure Friday, Annina Keller joins Scott Hanselman to show how Azure Static Web Apps provides built-in serverless API endpoints via integration with Azure services, including Azure App Service, Azure API Management, Azure Container Apps, and Azure Functions.
- 00:00 – Introduction
- 03:18 – Simple demo
- 10:30 – Demo with OAuth and API Management
- 17:50 – Wrap-up
- 18:40 – Resources
Source: Azure Friday
- Overview of API support in Azure Static Web Apps – https://aka.ms/azfr/729/01
- Use Static Web Apps API and API Management Authorizations to integrate third-party services – https://aka.ms/azfr/729/02
- API Management – Authorizations overview – https://aka.ms/azfr/729/03
- New API backend options in Azure Static Web Apps – https://aka.ms/azfr/729/04
- Create a Pay-as-You-Go account (Azure) – https://aka.ms/azfr/729/payg
- Create a free account (Azure) – https://aka.ms/azfr/729/free
Earlier this week I noticed that Microsoft launched the Azure Apps Demo Map website, a centralized way to see a some awesome resources available by Microsoft for building enterprise applications that leverage Azure technologies..
Most of the scenarios include an interactive user experience to explore the solution – including solution diagrams, live demos, source code and additional resources.
When exploring a scenario you can click on sections to see what technologies were used for that particular application. In the case of the Rewards application, it uses Azure Functions, Logic Apps, and App Service.
After exploring the interactive model you can head over to the GitHub project to download and run the code so that you can dig really deep in how the solution was built.
Let’s take a brief look at each of the projects.
Currently the Azure Apps Demo Map contains four applications as listed below.
Tailwind Traders is a fictitious retail company showcasing the future of intelligent application experiences. These reference apps are all powered by the Azure cloud, built with best-in-class tools, and made smarter through data and AI.
Visit the GitHub Project
SmartHotel360 is a fictitious smart hospitality company showcasing the future of connected travel. Their vision is to provide an intelligent and personalized experience to the guests.
Visit the GitHub Project
Rock, Paper, Scissors, Lizard, Spock
The geek version of the classic game. This sample shows a multilanguage application running on AKS with a front-end developed in Blazor and integrated with Azure Machine Learning and Azure Cognitive Services. Start the battle and find if you can beat our bot! VISIT PROJECT
Visit the GitHub Project
Contoso Air is a fictitious airline company. This lab shows how to create a website application that runs Node.JS Server that stores customer booked flights in an Azure Cosmos DB.
Unfortunately this project has no diagram and has been archived. However this project still contains valuable information for building a Node.JS + Cosmos DB application and running it on Azure.
Visit the GitHub Project
This is a great resource to learn how Azure can be used for an end to end solution for your business.
They have a feedback link so if you found the resource useful or you have suggestions please let them know. It would be cool to see this resource be expanded to include other applications that include Power BI, Power Apps, Azure DevOps, Dynamics, etc.
This is part of a series of posts about Azure App Configuration:
- Introduction to Azure App Configuration
- Creating your first centralized configuration
- Import/Export configurations
- Using Labels to
- Add features flags to your application using Feature Management
- Comparison of two sets of configurations
- Restoring to a previous configuration
- Using Azure App Configuration in your Azure DevOps Pipelines
In this post I’ll walk through what is Azure App Configuration and how to get started using it in your applications, whether their on-prem or in the cloud.
What is Azure App Configuration?
Before we get started with Azure App Configuration lets first look at what is it. Microsoft docs explains it as follows…
Azure App Configuration provides a service to centrally manage application settings and feature flags.Microsoft Docs – https://docs.microsoft.com/en-us/azure/azure-app-configuration/overview
Azure App Configuration helps you manage application settings and control their access centrally. It’s built on the simple concept of key-value pairs, and this service provides manageability, availability, and ease-of-use.
With modern programs, especially programs running in a cloud, you have many components that are distributed in nature. Spreading configuration settings across these components can lead to hard-to-troubleshoot errors during an application deployment. One key recommendation from the Twelve-Factor App guide is to separate configuration from code.
By leveraging Azure App Configuration to store all the settings for your application and secure their accesses in one place, you can simplify your deployment tasks and eases the burden of dealing with permutations of configurations created by multiple applications, dependencies, and environments.
Let’s get started!
Before we can begin you need to make sure you have the following installed and setup:
- An Azure Subscription. If you don’t have an Azure Account, you can sign up for one today for free and receive $200 in credits by selecting “Create a Free Azure Account…” or selecting “View->Command Palette” and searching for “Azure: Create an Account”
- Install Visual Studio or Visual Studio Code
Login to your Azure portal at https://portal.azure.com and click on the Create a resource link as shown here:
Next in the search field type ‘app configuration’ and press ‘Enter’. Then click on the Create button to create your Azure App Configuration. Currently this service is in preview but should be generally available soon.
When setting up your Azure App Configuration you will need to specify a few settings like Resource Name, Subscription, Resource Group, Location and Pricing Tier. Here is the resource that I’ll be setting up:
Now click on the Create button to have your resource created, which typically takes a minute or two. You will be notified in the Notifications area of the portal when your resource is ready.
Once your Azure App Configuration is created, navigate to it and you will see the following overview page that shows you your Endpoint for accessing your configurations along with other resource information.
Now navigate to the Configuration explorer to start creating configurations values. Click on the Create button and select Key-value.
Now create a simple configuration called ‘Color’ and give it a value of ‘Blue’ and click Apply.
In order to access your configurations you will need your connection string and key. Navigate to the Access keys section to view your keys and connection string information.
At the time of this writing, Azure App Configuration provides configuration support for ASP.NET Core, .NET Core, .NET Framework, Azure Functions in .NET Core, and Java Spring. For Feature Management, it supports ASP.NET Core, .NET Framework, and Java Spring.
Pricing and General Availability
Earlier this week the Azure App Configuration team announced that Azure App Configuration would be made generally available on February 19, 2020.
Initially there will be two types of plans, Free and Standard. Until February 19 both plans will continue to be free, and after February 19 all plans will be migrated to the Free plan. You can choose to stay on this plan or upgrade to the Standard plan. Pricing has remained unchanged from a previous post and will commence on February 19.
|Resources per subscription||1||Unlimited|
|Storage per resource||10 MB||1 GB|
|Key history||7 days||30 days|
|Requests per day||1,000 (HTTP status code 429 will be returned for all requests once the limit is reached)||Unlimited (First 200,000 included in the daily charge. Additional requests will be billed as overage)|
|Security functionality||Encryption with Microsoft-managed keys|
HMAC or AAD authentication
|All Free tier functionality plus:|
Encryption with customer-managed keys
Private Link support
|Cost||Free||US$1.20 per day, plus any overage charge at US$0.06 per 10,000 requests|
Azure App Configuration is a managed service that helps developers centralize their application and feature settings simply and securely.
I’ve been using it in my applications for the last few months and I love how easy it’s been to incorporate into my applications. I’m really excited that Azure App Configuration is nearing general availability later this month and I’m looking forward to what’s coming next, namely around Feature Management as this is still a simple offering and it will be nice when it’s available on more frameworks.
In my next post I’ll walk through in more detail about how you can import/export your configurations, compare them over time and use labels to filter certain values.
I came across an excellent blog post from the Azure App Service Team Blog – FAQ: App Service Domain (preview) and Custom Domains. Lots of great of questions and answers relating to Azure DNS and your custom domains.
If you have any questions or have run into issues with your custom domain and Azure this is a great resource, so check it out!
New Release of Azure Functions
A new release of Azure Functions is now available, version 1.0.10917. The main things in this release are:
- Application Insights integration (Preview)
- Native TypeScript support (preview)
- Improvements to binding extensibility for binding authors
- Miscellaneous bug fixes and improvements
New Experience for Azure Functions
The Azure Functions portal was also completely re-vamped with a new UI experience. Some of the improvements are:
- A dedicated browse blade for Function Apps.
- A tree view that allows viewing and managing multiple Function Apps
- Filters on subscription and app name, as well as an option to scope the view to just one app
- One-click access to all App Service platform features
- A convenient way to manage features that have already been configured
- Overall UI enhancements to be more consistent with the rest of the Azure portal
You can read more about the portal changes in the announcement blog.