Centralize your configuration with Azure App Configuration and Azure Functions

English Intermediate Development

Modern cloud applications are distributed in nature, almost every single application becomes part of a more complex distributed system. There are multiple applications running on different geographical locations and a single solution may have different services running on different platforms like App Services, Virtual Machines and Serverless functions etc. Managing application settings/configuration across these distributed instances is difficult, and when issues come up, it's even more difficult to troubleshoot. Having a centralized location to store your application configurations helps to solve these issues. In this session, you will learn how to implement a centralized configuration for your serverless Azure Functions as well as how you can leverage Feature Flags to modify a system's behaviour without changing any code. This session focuses on software architects and developers intending to design and implement modern enterprise applications. In my demos, I'll be showing best practices and lessons learned from real-world enterprise customer projects. Tags Azure App Configuration Azure Functions Azure Storage Azure Key Vault Serverless Centralized Configuration Feature Flags Configuration .NET Demos 1. Creating Azure App Configuration 2. Caching and updating configuration without an app restart 3. Using Feature Management 4. Automatic configuration backup and resiliency


Callon Campbell

Cloud Mavericks Inc., Solution Architect and Developer

Callon Campbell is a Solutions Architect, Developer and Microsoft MVP in Azure. With over 20 years of experience, he's been developing enterprise applications for web, desktop, mobile, and cloud-native applications using Microsoft Azure, .NET, ASP.NET, and SQL Server. Callon is also the co-creator of ReflectInsight .NET Logging framework and Live Log Viewer. He's passionate about learning new technologies and sharing his experience with fellow peers in the community. Callon is also the organizer of “Canada’s Technology Triangle .NET User Group” in Kitchener, Ontario. Callon can be reached on Twitter via @Flying_Maverick, and has a blog at https://TheFlyingMaverick.com.

Code of Conduct

We seek to provide a respectful, friendly, professional experience for everyone, regardless of gender, sexual orientation, physical appearance, disability, age, race or religion. We do not tolerate any behavior that is harassing or degrading to any individual, in any form. The Code of Conduct will be enforced.

Who does this Code of Conduct apply to?

All live stream organizers using the Global Azure brand and Global Azure speakers are responsible for knowing and abiding by these standards. Each speaker who wishes to submit through our Call for Presentations needs to read and accept the Code of Conduct. We encourage every organizer and attendee to assist in creating a welcoming and safe environment. Live stream organizers are required to inform and enforce the Code of Conduct if they accept community content to their stream.

Where can I get help?

If you are being harassed, notice that someone else is being harassed, or have any other concerns, report it. Please report any concerns, suspicious or disruptive activity or behavior directly to any of the live stream organizers, or directly to the Global Azure admins at team@globalazure.net. All reports to the Global admin team will remain confidential.

Code of Conduct for local live streams

We expect local organizers to set up and enforce a Code of Conduct for all Global Azure live stream.

A good template can be found at https://confcodeofconduct.com/, including internationalized versions at https://github.com/confcodeofconduct/confcodeofconduct.com. An excellent version of a Code of Conduct, not a template, is built by the DDD Europe conference at https://dddeurope.com/2020/coc/.