October 15, 2021


Maik van der Gaag, The Netherlands

Maik van der Gaag is the CTO of 3fifty, an experienced consultancy company with a strong focus on the Microsoft Cloud. He has over 15 years’ experience providing architecture, development, training and design expertise. During his works he works in a variety of projects ranging from Cloud Transformations to DevOps implementations. He loves to share is knowledge which was also one of the reasons why he founded the Dutch Cloud Meetup. Maik is a public speaker, writes blogs and organizes events. Microsoft has recognized him as Microsoft Azure MVP.

Security measures for Azure PaaS

17.30 - 18.30

One of the characteristics of Platform as a Service components in Azure is that they are open for the complete world by default Azure PaaS offers great services but you do not want to have them open by default in many situations. For this reasons I see many companies switching back the known functionalities (IaaS) but that should not be the case. In this session you will learn how to secure services like Azure Functions, Azure App Service, Azure SQL Databases with the use of Azure Front Door, Azure Private Link and Virtual Networks and many more.

Eduard Keilholz, The Netherlands

Eduard is a Cloud Solution Architect at 4Dotnet (The Netherlands). He likes to help customers with implementing and experiencing cloud technologies. He likes to create highly performant software and help team members reach a higher skill level of software development. He focusses is on the Microsoft development stack, mainly C# and the Microsoft Azure Cloud, and has a strong affinity with Angular. He enjoys speaking at (inter)national conferences and contributing to community events. In 2020, Microsoft has recognized these community activities with the Microsoft MVP Award for Azure.

Deploy your API secured, with a DevOps CI/CD pipeline

19.30 - 20.30

This session is all about DevOps and CI/CD. I will build an ASP.NET WebApi from scratch and deploy it using an Azure DevOps CI/CD pipeline and Infrastructure as Code. I will show you how different ARM templates are compared to the new Bicep DSL, and discuss the advantages of building and deploying in an automated fashion.



Code of Conduct

Our Pledge

We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.

We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.

Our Standards

Examples of behavior that contributes to a positive environment for our community include:

Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.

Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.


This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.


Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement: Edgar Tichelaar: [email protected] or Angela Schooneman: [email protected]. All complaints will be reviewed and investigated promptly and fairly.

All community leaders are obligated to respect the privacy and security of the reporter of any incident.

Enforcement Guidelines

Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:

  1. Correction
    Community Impact: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
  2. Consequence: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
  3. Warning
    Community Impact: A violation through a single incident or series of actions.
  4. Consequence: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
  5. Temporary Ban
    Community Impact: A serious violation of community standards, including sustained inappropriate behavior.
  6. Consequence: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
  7. Permanent Ban
    Community Impact: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.
  8. Consequence: A permanent ban from any sort of public interaction within the community.


This Code of Conduct is adapted from the Contributor Covenant, version 2.0, available at


Eduard Keilholz

Eduard is the initiator of DotnetFriday. Eduard is very passionate about technology and techniques required to create high quality software! He likes to share this passion by organizing sessions for technologies that enable you to write better software. He is responsible for the general event and partly responsible for speaker and session selection.

Jan de Vries

Jan has been developing software for well over a decade. Currently, he is working at 4Dotnet as a Cloud Solution Architect/Developer and is awarded by Microsoft with the Microsoft MVP award. Jan is, together with Eduard intimately involved in organizing DotnetFriday. He is partly responsible for speaker and session selection.

Jan-Willem de Wagt

Jan Willem is the engagement officer of DotnetFriday. He is very eager to meet new people and works hard on making each DotnetFriday event a success. His mission is to fill our venue with attendees.