July 7, 2026

Azure Networking Unlocked: Secure Azure Functions, Virtual Network Manager & Infrastructure as Code with Rex de Koning [MVP-MCT]

Azure networking has evolved far beyond simply connecting virtual machines. In this episode, we explore how modern Azure networking enables organizations to build secure, scalable, and fully automated cloud environments using Azure Functions, Azure Virtual Network Manager, and Infrastructure as Code.

We begin by discussing how Azure Functions can securely access private resources without exposing services to the public internet. You'll learn how Virtual Network integration, private endpoints, and network isolation help organizations protect sensitive workloads while maintaining the flexibility of serverless computing. These capabilities are becoming essential for building secure cloud-native applications. We also cover the networking options available for Azure Functions across different hosting plans and the architectural decisions behind them.

Next, we dive into Azure Virtual Network Manager and how it simplifies enterprise-scale networking. Instead of manually configuring hundreds of virtual networks, administrators can centrally manage connectivity, security rules, hub-and-spoke or mesh topologies, and policy enforcement across multiple subscriptions and regions. The discussion highlights why centralized network governance is becoming increasingly important as Azure environments continue to grow.

Finally, we examine why Infrastructure as Code is now a core requirement for modern Azure networking. Using tools such as Bicep or Terraform, organizations can deploy repeatable, version-controlled, and auditable network infrastructure, reducing configuration drift while improving reliability and security. Whether you're an Azure architect, cloud engineer, or infrastructure professional, this episode provides practical insights into designing secure, automated, and enterprise-ready Azure networking environments.

Securing Azure Functions within a Virtual Network is vital for protecting your cloud applications, a topic thoroughly explored in the podcast "Azure Networking Unlocked." By integrating these functions into a virtual network, you limit exposure to potential threats and enhance your overall security posture. Additionally, utilizing Infrastructure as Code (IaC) streamlines your deployment processes, a concept emphasized in "Azure Networking Unlocked." This automation reduces manual errors and saves time, allowing you to focus on building robust solutions. With IaC, you achieve consistent deployments, which fosters collaboration between development and operations teams, ultimately creating a more efficient workflow in your Azure environment.

Key Takeaways

Integrate Azure Functions with a Virtual Network to enhance security and limit exposure to threats.
Utilize Infrastructure as Code (IaC) to automate deployments, ensuring consistency and reducing manual errors.
Implement strict access controls and use HTTPS to secure communications for Azure Functions.
Leverage Azure Key Vault for managing secrets securely, protecting sensitive information from unauthorized access.
Use Network Security Groups (NSGs) to filter traffic and segment your Azure resources effectively.
Adopt Zero Trust principles to verify every request, enhancing security across your Azure environment.
Regularly monitor your network using Azure Monitor and Azure Network Watcher to maintain performance and security.
Follow best practices for API security, including using OAuth 2.0 and managing identities for access control.

Azure Networking Unlocked: Prerequisites

Azure Functions Overview

Azure Functions allow you to run code without managing servers. This serverless architecture simplifies application development. You can build web APIs, respond to database changes, process IoT streams, and manage scheduled tasks. Azure Functions support various automation scenarios, making them versatile for cloud applications.

You can trigger functions using different events. For example, an Azure Blob Storage trigger automates actions when files are uploaded or modified. Azure Queue triggers process incoming orders or validate data asynchronously. This flexibility helps you create efficient workflows in your cloud environment.

Virtual Network Basics

A virtual network (VNet) in Azure provides a secure and isolated environment for your resources. It allows you to connect Azure services and on-premises networks securely. By using VNets, you eliminate exposure to the public internet, enhancing your overall security.

Key features of VNets include:

Private Network Space: VNets create a dedicated space for your resources.
Network Security Groups (NSGs): NSGs act as virtual firewalls, filtering traffic to and from your resources.
Isolation and Access Control: VNets restrict access to authorized networks, ensuring compliance with security requirements.

Understanding these components is crucial for managing and optimizing your Azure networking resources effectively.

Infrastructure as Code Essentials

Infrastructure as Code (IaC) is vital for automating your Azure deployments. It allows you to define your infrastructure using code, reducing manual errors and speeding up deployment processes. Key elements of IaC include:

Ease of Deployment: Automate the setup of your resources.
Consistency: Ensure uniformity across different environments.
Scalability: Quickly adjust your infrastructure to meet changing demands.
Auditability: Track changes using version control systems like Git.

You can use tools like Azure Resource Manager (ARM) templates, Terraform, and Bicep to implement IaC. These tools help you manage your Azure resources efficiently, ensuring that your cloud environment remains secure and compliant.

By understanding these prerequisites, you can build a solid foundation for securing Azure Functions, managing virtual networks, and implementing Infrastructure as Code in your Azure environment.

Architecture for Secure Azure Function App

High-Level Architecture

To create a secure Azure Function App, you should integrate it with a virtual network (VNet). This integration allows your function to communicate securely with other resources in your Azure environment. The recommended high-level architecture includes the following elements:

Recommendation	Benefit
Integrate with a virtual network and use private endpoints	Secures function apps by restricting access to your internal network and preventing exposure to the public internet. Virtual network integration and private endpoints aren't available in the Consumption hosting plan.

This architecture ensures that your functions operate within a controlled environment, minimizing the risk of unauthorized access.

Key Components

When deploying a secure Azure Function App, several key components play a crucial role in maintaining security and functionality:

Component	Description
Require HTTPS	Ensures secure communication by enforcing HTTPS and the latest TLS version.
Manage access keys	Protects function endpoints by requiring access keys unless set to anonymous.
Deploy within a virtual network	Enhances security by isolating the function app within a private network.
Use Azure API Management for authentication	Provides additional security options for incoming requests and can restrict access based on IP.

These components work together to create a robust security framework for your Azure Functions, ensuring that only authorized users can access your applications.

Security Considerations

Security is paramount when deploying Azure Functions. You must be aware of potential risks and implement strategies to mitigate them. Here are some common security risks associated with Azure Function Apps:

Overly permissive policies: These can lead to insecure deployments that bypass security checks.
Exposure of APIs without proper authentication: This creates direct backdoors into the environment, making it easier for attackers to exploit vulnerabilities.
Insecure coding practices: Vulnerable function code can expose sensitive data or resources.

To mitigate these risks, consider the following strategies:

Implement strict controls on ARM templates and enforce well-defined security policies.
Use Azure API Management to control access to serverless function APIs.
Monitor misconfigurations flagged in Azure Security Center and implement remediation measures.

By addressing these security considerations, you can significantly enhance the security of your Azure Function App and protect your cloud resources.

Create Virtual Network

Creating a virtual network (VNet) in Azure is essential for establishing a secure environment for your cloud resources. Follow this step-by-step guide to create a virtual network using both the Azure Portal and Azure CLI.

Step-by-Step Guide

Using Azure Portal

Navigate to your Azure portal.
Click on the Create resource option.
Type in virtual network in the search bar and click on Create.
Fill in details about the virtual network:
- Subscription: Choose your subscription.
- Resource Group: Select or create a new resource group.
- Name: Enter the name of your virtual network.
- Region: Choose the region for your virtual network.
Click on Next: IP Addresses and enter the details:
- IPv4 address space: Enter the IPV4 address range in CIDR notation.
- Subnet: Create a subnet for your virtual network.
Click on Next: Security tab and choose your security settings.
Click on Review + create and wait for validations.
Click on Create to finalize the virtual network.

Using Azure CLI

You can also create a virtual network using the Azure CLI. Here’s how:

Open Azure Cloud Shell from the top menu bar.
Select Bash.

Use the following command to create a virtual network named vnet1 with an address prefix of 10.1.0.0/16:

az network vnet create --name vnet1 --resource-group <your-resource-group> --address-prefix 10.1.0.0/16

Refresh your resources to verify that vnet1 appears under All resources.

Configure Subnets and Security Groups

After creating your virtual network, configure subnets and security groups to enhance security:

Subnets: Create subnets within your virtual network to group resources with similar business functions. This segmentation improves management and security.
Network Security Groups (NSGs): Use NSGs to manage traffic between different tiers of your network. Implement strict security rules to control traffic flow, avoiding broad allow rules.

Best Practice	Description
Virtual Networks	Provide network-level containment of resources without adding traffic between two virtual networks.
Network Security Groups (NSG)	Control traffic between resources in virtual networks and external networks, allowing for granular segmentation.
Application Security Groups (ASG)	Group VMs under an application tag to define and apply traffic rules.
Azure Firewall	Filter traffic between cloud resources, the internet, and on-premises resources, enhancing security.
Traffic Analytics	Analyze network flow logs to validate segmentation policies and monitor traffic behavior.

By following these steps, you can create a virtual network that secures your Azure resources effectively.

Configure Azure Functions

Create Function App

To create a function app, you need to follow a few essential steps. Start by logging into the Azure portal. Then, navigate to the Create a resource section. Select Function App from the list of available resources. Fill in the required details, such as the subscription, resource group, and name of your function app. Choose the runtime stack that suits your application needs. Finally, click Create to deploy your function app.

When you create a function app, ensure you implement secure operation practices. Use Azure Active Directory for authentication. This step helps protect your function app from unauthorized access. Additionally, manage access keys carefully. Require HTTPS for all communications to secure data in transit. Isolate your function apps to enhance security and secure the SCM endpoint to prevent unauthorized access.

Networking Settings

Networking settings play a crucial role in securing your Azure Function Apps. Here are some essential settings to consider:

Networking Setting	Description
Virtual Networks	Integrate your function app with a virtual network to enhance security and control access.
Private Endpoints	Use private endpoints to connect securely to Azure services, ensuring traffic does not traverse the public internet.
Key Vault References	Utilize Azure Key Vault for centralized secrets management, allowing secure access to sensitive information without code changes.
Storage Account Security	Ensure your storage account is secured with service endpoints or private endpoints to restrict access.

By configuring these networking settings, you can significantly enhance the security of your Azure Function Apps.

Integrate with Virtual Network

Integrating your function app inside a virtual network is vital for maintaining a secure environment. This integration allows you to restrict outbound connections to specific, trusted VNets only. It ensures that your function app is accessible only from a private network, which enhances security.

Here are some key features of virtual network integration:

Feature	Description
Outbound Connection Restriction	Virtual Network integration allows Azure Functions to restrict outbound connections to specific, trusted VNets only, enhancing security.
Private Network Accessibility	The integration ensures that the Function App is accessible only from a private network, maintaining a secure environment.
Compliance and Data Privacy	This feature is particularly valuable for organizations that prioritize network security, compliance, and data privacy while using serverless computing in Azure.

By following these steps and integrating your function app with a virtual network, you can create a secure and efficient cloud environment for your applications.

Enhance Security with API Management

Overview of API Management

API Management serves as a crucial layer for securing your Azure Functions. It allows you to create, publish, and manage APIs in a secure environment. By using API Management, you can control access to your Azure Function Apps and monitor their usage effectively. This service provides built-in security features that protect your functions from unauthorized access and potential attacks.

Here are some key security mechanisms offered by API Management:

Security Mechanism	Description
Validation Policies	Validate API requests and responses against an OpenAPI schema, providing extra protection against threats.
Microsoft Defender for APIs	Offers full life cycle protection and detects vulnerabilities using machine learning and rule-based detections.
Private Endpoints	Securely connect to Azure Functions over a private IP, reducing unauthorized access risks.
Application Gateway	Protects API Management instances from web application exploits and enables hybrid connectivity.

Securing Azure Functions

Securing your Azure Functions through API Management involves several strategies. First, you should use Microsoft Entra ID as the default authentication method. This approach ensures that only authorized users can access your APIs. Additionally, configure the API Management developer portal to authenticate developer accounts using Microsoft Entra ID. This step enhances security by managing user identities effectively.

You can also protect your APIs using the OAuth 2.0 protocol with Microsoft Entra ID. This method improves client identification for auditing purposes and reduces the burden on clients to protect secrets compared to using preshared keys. Avoid local authentication methods; instead, rely on Microsoft Entra ID for data plane access.

Here are some recommended methods for securing Azure Functions through API Management:

Use Microsoft Entra ID as the default authentication method for API Management.
Protect APIs using the OAuth 2.0 protocol with Microsoft Entra ID.
Store secrets for API Management in Azure Key Vault for secure access and updates.
Use Managed Service Identity generated by Microsoft Entra ID for secure access to other resources like Azure Key Vault.

Best Practices for API Security

Implementing best practices for API security is essential for maintaining a secure cloud environment. Here are some recommendations:

Recommendation	Benefit
Back ends should only accept traffic from the API gateways and block all other traffic.	This prevents malicious traffic from bypassing the security measures in place.
Use different user-assigned managed identities for different APIs.	Each API can have an independent identity, supporting segmentation goals through least privilege access.
Require clients to authenticate with OAuth 2.0 flows when possible.	This improves client identification for auditing and eliminates key rotation burdens.

Additionally, establish a security baseline by reviewing the security baseline for API Management. Protect the deployment pipeline by ensuring only authorized individuals have access. Evaluate data sensitivity to ensure protection throughout its lifecycle. Develop segmentation strategies on shared gateways to restrict access.

By following these practices, you can significantly enhance the security of your Azure Functions and protect your cloud resources effectively.

Automate with Infrastructure as Code

Introduction to ARM Templates

Azure Resource Manager (ARM) templates play a crucial role in automating your Azure infrastructure. They provide a declarative method for defining and deploying Azure resources. With ARM templates, you can ensure consistency and repeatability across different environments. This consistency is vital for maintaining a secure and reliable cloud environment. Additionally, you can integrate ARM templates into CI/CD pipelines for automated deployment, streamlining your workflow.

Writing IaC for Azure Functions

When you write Infrastructure as Code (IaC) for Azure Functions, you focus on security and efficiency. Start by implementing secure coding practices and frameworks. Use Azure Key Vault to store secrets securely. This practice helps protect sensitive information from unauthorized access. Leverage Azure DevOps for continuous integration and continuous deployment (CI/CD) to ensure secure deployment of your functions. Monitoring function logs is essential to identify potential security threats. You should also configure network security policies, including firewalls and VPNs, to enhance your security posture.

Deploying with Azure DevOps

Deploying Azure Functions using Azure DevOps pipelines involves several key steps:

Commit template and parameter files to source control.
Run validation and lint checks to ensure code quality.
Review what-if output to understand potential changes.
Deploy to a test environment for initial verification.
Verify outputs, tags, and resource health to ensure everything works as expected.
Approve and deploy to production once you confirm that everything is functioning correctly.

By following these steps, you can automate the deployment of your Azure Functions effectively. This automation not only saves time but also reduces the risk of human error, allowing you to focus on building robust applications.

Best Practices for Azure Networking

Security Best Practices

To secure your Azure networking environment, you should implement several best practices. Start by adopting Zero Trust principles. This approach eliminates trust based solely on network location. Instead, verify every request as if it originates from an untrusted network. Use Conditional Access to control resource access based on various factors, such as user identity and device health.

Consider enabling just-in-time VM access to reduce exposure to attacks. This feature limits the time that your virtual machines are accessible, minimizing potential vulnerabilities. Utilize Azure Bastion for secure remote access without exposing public IPs. This service allows you to connect to your VMs directly through the Azure portal, enhancing security.

Additionally, enable DDoS protection to preserve availability for your internet-facing workloads. Deploy virtual network appliances for enhanced security at higher OSI layers. These appliances can provide advanced threat protection and traffic filtering.

Performance Optimization

Optimizing performance in your Azure networking environment is crucial for maintaining efficient operations. Start by ensuring that your virtual networks (VNets) are properly configured. Use subnets to segment your network and improve performance. This segmentation allows you to manage traffic more effectively and enhances security.

Consider implementing Azure Traffic Manager to distribute traffic across multiple regions. This service improves responsiveness and availability by directing users to the nearest endpoint. Additionally, leverage Azure CDN to cache content closer to users, reducing latency and improving load times.

Regularly review your network configurations and adjust them based on performance metrics. Use tools like Azure Monitor to track network performance and identify bottlenecks.

Monitoring and Logging

Effective monitoring and logging are essential for maintaining a secure and efficient Azure networking environment. Utilize Azure Monitor to collect, analyze, and act on telemetry from your cloud and on-premises environments. This comprehensive solution helps you gain insights into your network's performance and security.

Set up an Azure Log Analytics Workspace to collect and analyze data generated by your resources. This workspace centralizes log collections and allows for complex log analysis using KQL. Use Azure Network Watcher for network performance monitoring and diagnostic tools. This service provides insights into your network's health and performance.

Automate repetitive tasks critical for network monitoring and management using Azure Automation or Logic Apps. These tools help streamline your operations and ensure that you respond quickly to any issues.

By following these best practices, you can enhance the security, performance, and monitoring of your Azure networking environment, ensuring that your cloud resources remain secure and efficient.

In this blog, you learned the importance of securing Azure Functions and managing network configurations effectively. By integrating Azure Functions within a virtual network (VNet), you enhance security and control access. Key practices include utilizing Azure Key Vault for managing secrets and implementing Network Security Groups (NSGs) to segment traffic.

Adopting Infrastructure as Code (IaC) streamlines your deployments, ensuring consistency and reducing errors. Remember to implement best practices such as Conditional Access and Zero Trust principles to safeguard your cloud environment. By following these guidelines, you can create a secure and efficient Azure networking setup that supports your applications.

FAQ

What are Azure Functions?

Azure Functions are serverless compute services that allow you to run code in response to events. You can build APIs, process data, and automate tasks without managing servers.

How do I secure my Azure Functions?

You can secure Azure Functions by using HTTPS, managing access keys, integrating with Azure Active Directory, and deploying them within a virtual network.

What is a Virtual Network in Azure?

A Virtual Network (VNet) is a private network in Azure that allows you to securely connect Azure resources. It isolates your resources from the public internet, enhancing security.

What is Infrastructure as Code (IaC)?

Infrastructure as Code (IaC) is a practice that allows you to manage and provision infrastructure using code. This approach automates deployments, ensures consistency, and reduces manual errors.

How do I create a Virtual Network?

You can create a Virtual Network using the Azure Portal or Azure CLI. Follow the step-by-step guide in the blog to set up your VNet effectively.

What are Network Security Groups (NSGs)?

Network Security Groups (NSGs) are used to filter network traffic to and from Azure resources. They contain rules that allow or deny traffic based on source and destination IP addresses.

How can I monitor my Azure networking environment?

You can monitor your Azure networking environment using Azure Monitor and Azure Network Watcher. These tools provide insights into performance, security, and network health.

What are the best practices for securing Azure Functions?

Best practices include using Azure API Management for access control, implementing strict access policies, and regularly reviewing security configurations to mitigate risks.

🚀 Want to be part of m365.fm?

Then stop just listening… and start showing up.

👉 Connect with me on LinkedIn and let’s make something happen:

🎙️ Be a podcast guest and share your story
🎧 Host your own episode (yes, seriously)
💡 Pitch topics the community actually wants to hear
🌍 Build your personal brand in the Microsoft 365 space

This isn’t just a podcast — it’s a platform for people who take action.

🔥 Most people wait. The best ones don’t.

👉 Connect with me on LinkedIn and send me a message:
"I want in"

Let’s build something awesome 👊

1
00:00:00,000 --> 00:00:05,000
And everyone and welcome back to the MC65FFM podcast.

2
00:00:05,000 --> 00:00:08,040
Cloud adoption has never been faster,

3
00:00:08,040 --> 00:00:10,640
but with the speed comes complexity.

4
00:00:10,640 --> 00:00:14,320
Networks are no longer just cables and switches.

5
00:00:14,320 --> 00:00:18,160
They are software-different, automated, globally distro,

6
00:00:18,160 --> 00:00:22,920
distribbed and expected to be true from day one.

7
00:00:22,920 --> 00:00:24,800
Whenever you deploy Azure Function,

8
00:00:24,800 --> 00:00:26,840
building landings, also managing Hondas

9
00:00:26,840 --> 00:00:30,240
of virtual networks across multiple subscriptions,

10
00:00:30,240 --> 00:00:32,720
network has become one of the most critical skills

11
00:00:32,720 --> 00:00:34,760
in Azure ecosystem.

12
00:00:34,760 --> 00:00:38,360
Today's guest has spent nearly three decades in IT,

13
00:00:38,360 --> 00:00:40,080
starting as a software developer

14
00:00:40,080 --> 00:00:42,720
before moving into the system engineering,

15
00:00:42,720 --> 00:00:44,200
networking cloud infrastructure,

16
00:00:44,200 --> 00:00:48,120
and ultimately becoming one of Microsoft's most recognized

17
00:00:48,120 --> 00:00:50,040
experts in Azure networking.

18
00:00:50,040 --> 00:00:53,400
He's a Microsoft MVP, Microsoft Certificate Trainer,

19
00:00:53,400 --> 00:00:56,440
Community Organizer, Speaker and Pesonet,

20
00:00:56,440 --> 00:00:58,960
about Advocate for Infrastructure as a Code

21
00:00:58,960 --> 00:01:01,160
and secure ground architecture.

22
00:01:01,160 --> 00:01:03,160
Yeah, please welcome Rex the Kronik.

23
00:01:03,160 --> 00:01:05,080
- Thank you very much.

24
00:01:05,080 --> 00:01:06,440
That was some intro.

25
00:01:06,440 --> 00:01:11,800
- Yes, welcome everybody.

26
00:01:11,800 --> 00:01:13,120
- Yeah, thank you.

27
00:01:13,120 --> 00:01:16,400
Yeah, you have been working in IT for nearly 30 years.

28
00:01:16,400 --> 00:01:18,720
That's, what's your name?

29
00:01:18,720 --> 00:01:21,320
- Well, 20 years this year, to be honest, yeah.

30
00:01:21,320 --> 00:01:24,000
I started basically, basically, to the day almost,

31
00:01:24,000 --> 00:01:27,400
I started somewhere in June of July, 1996.

32
00:01:27,400 --> 00:01:28,840
(laughs)

33
00:01:28,840 --> 00:01:30,000
- Awesome.

34
00:01:30,000 --> 00:01:32,840
But how did you, yeah,

35
00:01:32,840 --> 00:01:34,520
how did you start your career?

36
00:01:34,520 --> 00:01:37,520
And especially how did you evolve

37
00:01:37,520 --> 00:01:39,120
into the Microsoft ecosystem?

38
00:01:39,120 --> 00:01:43,640
- Well, how I started, that was kind of easy.

39
00:01:43,640 --> 00:01:46,800
It's all started in the beginning of the 80s,

40
00:01:46,800 --> 00:01:49,880
basically, with a Commodore 64,

41
00:01:49,880 --> 00:01:52,840
which some people might have heard of.

42
00:01:52,840 --> 00:01:54,240
(laughs)

43
00:01:54,240 --> 00:01:57,880
- Yeah, and that grew my interest in computers

44
00:01:57,880 --> 00:02:00,840
and, well, IT wasn't the thing at that time,

45
00:02:00,840 --> 00:02:02,440
but it was the start of it.

46
00:02:02,440 --> 00:02:05,720
From there, I started with a PC,

47
00:02:05,720 --> 00:02:09,680
an XT machine with a whopping,

48
00:02:09,680 --> 00:02:12,240
I think we had one megabyte of RAM.

49
00:02:12,240 --> 00:02:17,720
And now I started IT training.

50
00:02:17,720 --> 00:02:20,240
It's cool that we had a special training for that

51
00:02:20,240 --> 00:02:21,280
in the Netherlands.

52
00:02:22,440 --> 00:02:26,560
And from there, I did an internship at a company

53
00:02:26,560 --> 00:02:28,200
and also started working there.

54
00:02:28,200 --> 00:02:31,120
First, just developing websites

55
00:02:31,120 --> 00:02:36,280
because that was an up and coming thing in 1995,

56
00:02:36,280 --> 00:02:38,920
when not everybody had internet yet.

57
00:02:38,920 --> 00:02:41,720
(laughs)

58
00:02:41,720 --> 00:02:44,680
Yeah, and started with creating websites,

59
00:02:44,680 --> 00:02:46,040
doing some programming,

60
00:02:46,040 --> 00:02:50,840
well, kind of evolved in that,

61
00:02:52,080 --> 00:02:55,320
decided to make SWITS to network and system engineering

62
00:02:55,320 --> 00:02:58,680
because that was more my thing than really developing.

63
00:02:58,680 --> 00:03:03,240
So I did a lot of years doing on-prem management stuff.

64
00:03:03,240 --> 00:03:07,760
And then something called PowerShell came along

65
00:03:07,760 --> 00:03:12,240
and went by my background in development.

66
00:03:12,240 --> 00:03:15,000
I started to pick that up and also because it's,

67
00:03:15,000 --> 00:03:18,320
well, for automation, it's a great tool, of course.

68
00:03:20,000 --> 00:03:25,000
Yeah, and from there in 2003, no, 2012, I think 2013,

69
00:03:25,000 --> 00:03:31,840
there was some company called Amazon

70
00:03:31,840 --> 00:03:33,760
that did something with web services.

71
00:03:33,760 --> 00:03:36,400
We started looking at that,

72
00:03:36,400 --> 00:03:38,680
worked with it for a couple of years,

73
00:03:38,680 --> 00:03:40,920
did some certifications in there.

74
00:03:40,920 --> 00:03:45,480
And then, yeah, I went to another employer,

75
00:03:45,480 --> 00:03:48,400
they used something called Microsoft Azure

76
00:03:48,400 --> 00:03:50,120
because it was the Microsoft Azure yet.

77
00:03:50,120 --> 00:03:54,360
It was called Windows Azure Pack.

78
00:03:54,360 --> 00:03:56,560
(laughs)

79
00:03:56,560 --> 00:03:58,280
That was really the beginning.

80
00:03:58,280 --> 00:04:02,760
So basically what we now would call Azure Local,

81
00:04:02,760 --> 00:04:06,520
basically, that was Windows Azure Pack.

82
00:04:06,520 --> 00:04:09,800
And then from there, we grew to Microsoft Azure.

83
00:04:09,800 --> 00:04:12,880
Yeah, started working with that.

84
00:04:12,880 --> 00:04:16,800
And of course, also the automation came into play again.

85
00:04:16,800 --> 00:04:20,480
So my PowerShell knowledge was of good use there.

86
00:04:20,480 --> 00:04:24,120
Started working more and more with it.

87
00:04:24,120 --> 00:04:25,920
Well, it became bigger and bigger

88
00:04:25,920 --> 00:04:28,080
to what it is today, basically.

89
00:04:28,080 --> 00:04:33,960
Yeah, and from my background of system and network engineering,

90
00:04:33,960 --> 00:04:36,320
I also do a lot of course with Azure networking,

91
00:04:36,320 --> 00:04:39,480
well, because as you mentioned in the intro,

92
00:04:39,480 --> 00:04:44,440
I mean, all the resources and VMs and all the services are nice,

93
00:04:44,440 --> 00:04:46,320
but without networking, nothing works.

94
00:04:47,320 --> 00:04:50,160
And yeah, grew from that.

95
00:04:50,160 --> 00:04:52,920
It's some sessions about it.

96
00:04:52,920 --> 00:04:56,000
And here we are, basically.

97
00:04:56,000 --> 00:05:01,600
- Anything you missed from the transition from IBS

98
00:05:01,600 --> 00:05:03,200
to Microsoft Azure?

99
00:05:03,200 --> 00:05:05,480
(laughs)

100
00:05:05,480 --> 00:05:08,640
- Well, honestly, that's been so long ago,

101
00:05:08,640 --> 00:05:10,000
I can't remember.

102
00:05:10,000 --> 00:05:11,800
(laughs)

103
00:05:11,800 --> 00:05:16,200
Yeah, so basically a lot of functionalities are the same, of course.

104
00:05:16,520 --> 00:05:20,640
Only with different names and different dialects,

105
00:05:20,640 --> 00:05:23,320
dialects versions, let's say, like that.

106
00:05:23,320 --> 00:05:28,080
- Yeah, and many people in company think it's the cloud,

107
00:05:28,080 --> 00:05:30,040
Microsoft handles the networking.

108
00:05:30,040 --> 00:05:33,080
Why is that such a dangerous misconception?

109
00:05:33,080 --> 00:05:39,800
- Mainly because networking in Azure

110
00:05:39,800 --> 00:05:42,560
works completely different than most people think.

111
00:05:45,720 --> 00:05:48,760
If you are accustomed with on-premise networking,

112
00:05:48,760 --> 00:05:53,200
you have your networks, you have your subnet,

113
00:05:53,200 --> 00:05:58,200
you have your feelings, it's all kind of clear what it does.

114
00:05:58,200 --> 00:06:03,280
In Azure, it's a bit different,

115
00:06:03,280 --> 00:06:06,760
although you have the concept of virtual networks

116
00:06:06,760 --> 00:06:09,440
and the concept of subnet,

117
00:06:09,440 --> 00:06:13,440
well, you don't have feelings, but that's your finance, basically.

118
00:06:14,800 --> 00:06:17,680
Basically, all the routing and all the differentiation

119
00:06:17,680 --> 00:06:20,640
in the different networks, let's say, like that,

120
00:06:20,640 --> 00:06:23,960
is not done in a network concept.

121
00:06:23,960 --> 00:06:27,400
It's done on the virtual machine or on the resource itself.

122
00:06:27,400 --> 00:06:34,720
So basically, besides some resources that really need

123
00:06:34,720 --> 00:06:40,120
a different subnet, like firewall or virtual network gateway,

124
00:06:40,120 --> 00:06:44,520
for example, basically setting up subnets

125
00:06:44,520 --> 00:06:47,080
isn't really necessary because everything is handled

126
00:06:47,080 --> 00:06:49,920
on the virtual machine, and it's much more important

127
00:06:49,920 --> 00:06:52,200
to have your network security groups

128
00:06:52,200 --> 00:06:57,440
as a first line of defense over to shield of your machines

129
00:06:57,440 --> 00:07:02,360
or your resources, then thinking of the concept

130
00:07:02,360 --> 00:07:03,600
of virtual networks.

131
00:07:03,600 --> 00:07:07,480
- And I think we have two concepts.

132
00:07:07,480 --> 00:07:12,480
We have, yeah, we have Havensburg and we have Virgil Alain.

133
00:07:12,480 --> 00:07:17,480
One, show companies choose Havensburg and Ben, Virgil Alain.

134
00:07:17,480 --> 00:07:21,920
- Well, it's kind of a consultant answer,

135
00:07:21,920 --> 00:07:24,120
but it depends on what you want, of course.

136
00:07:24,120 --> 00:07:31,480
Huppensburg is in the basis also a legacy thing

137
00:07:31,480 --> 00:07:34,360
that comes from the young primith world.

138
00:07:34,360 --> 00:07:38,880
On the one hand, it doesn't make much sense

139
00:07:38,880 --> 00:07:40,920
to set it up like that in Azure

140
00:07:40,920 --> 00:07:43,560
and the other end, a lot of companies do it

141
00:07:43,560 --> 00:07:46,920
because it works in it's familiar territory.

142
00:07:46,920 --> 00:07:50,560
But of course, it also has its drawbacks.

143
00:07:50,560 --> 00:07:53,320
For example, if you want on-premise connectivity

144
00:07:53,320 --> 00:07:58,320
from one branch to connect to an on-premise in another branch,

145
00:07:58,320 --> 00:08:02,880
that's not gonna work with Huppensburg by default.

146
00:08:02,880 --> 00:08:07,760
There are some ways by using a router or those kind of things

147
00:08:07,760 --> 00:08:08,840
to make it work,

148
00:08:09,760 --> 00:08:13,000
but that's one of the reasons why Virgil one was created

149
00:08:13,000 --> 00:08:15,520
by Microsoft.

150
00:08:15,520 --> 00:08:19,680
It's certainly not the Holy Grail, but it does what it does.

151
00:08:19,680 --> 00:08:24,960
And because it's a managed service, it makes lives

152
00:08:24,960 --> 00:08:28,520
and routing a lot easier for a lot of people.

153
00:08:28,520 --> 00:08:30,600
The big drawback with it at the moment

154
00:08:30,600 --> 00:08:33,800
and yeah, we can only hope that it will improve

155
00:08:33,800 --> 00:08:35,360
is that because it's a managed service,

156
00:08:35,360 --> 00:08:38,280
you have no idea what's going on under the hood.

157
00:08:38,280 --> 00:08:41,280
So when things don't work, it's quite a hassle

158
00:08:41,280 --> 00:08:44,640
to find out what the problem is and how to fix it.

159
00:08:44,640 --> 00:08:47,520
So that's why you see more and more

160
00:08:47,520 --> 00:08:50,760
that people are using route server instead of virtual one.

161
00:08:50,760 --> 00:08:56,920
- I think one other hot topic or actually topic

162
00:08:56,920 --> 00:08:59,160
is in the role Microsoft ecosystem,

163
00:08:59,160 --> 00:09:02,400
but especially in Azure, it's multi-region.

164
00:09:02,400 --> 00:09:05,560
What are the biggest network challenges there?

165
00:09:06,560 --> 00:09:10,560
- Well, with multi-region, you have of course

166
00:09:10,560 --> 00:09:14,960
a couple of challenges besides the network challenge.

167
00:09:14,960 --> 00:09:17,280
You got to make a decision.

168
00:09:17,280 --> 00:09:19,960
For example, do I have a hot configuration?

169
00:09:19,960 --> 00:09:23,960
So do I have all my resources in another region or not?

170
00:09:23,960 --> 00:09:27,240
Or in example, for a DR construction?

171
00:09:27,240 --> 00:09:30,480
Am I gonna build up my resources if one region fails?

172
00:09:30,480 --> 00:09:33,320
Which is probably not gonna work

173
00:09:33,320 --> 00:09:36,440
with all the resource availability problems there are

174
00:09:36,440 --> 00:09:37,280
at this time.

175
00:09:37,280 --> 00:09:41,080
But another thing you need to think about of course

176
00:09:41,080 --> 00:09:44,320
with multi-region is the latency.

177
00:09:44,320 --> 00:09:48,840
For example, if we're here in Europe,

178
00:09:48,840 --> 00:09:51,800
so when we play stuff in Western Europe

179
00:09:51,800 --> 00:09:53,760
and then we can know to know the Europe

180
00:09:53,760 --> 00:09:58,760
or Germany or Sweden or the UK,

181
00:10:00,040 --> 00:10:03,440
that's all pretty much next door.

182
00:10:03,440 --> 00:10:08,520
But for example, if you have a region in Singapore

183
00:10:08,520 --> 00:10:13,600
or towards China, which is a lot further away from here,

184
00:10:13,600 --> 00:10:15,960
you really need to think about your latency

185
00:10:15,960 --> 00:10:19,680
because some personalities might not work

186
00:10:19,680 --> 00:10:22,200
the way you expect with longer latencies

187
00:10:22,200 --> 00:10:26,080
or your responses might be delayed in the late is a big word

188
00:10:26,080 --> 00:10:27,480
because it's not seconds of course.

189
00:10:27,480 --> 00:10:32,480
But your latency is becoming greater and greater.

190
00:10:32,480 --> 00:10:35,080
And another thing with multi-region of course,

191
00:10:35,080 --> 00:10:37,960
is if you go from one region to the other,

192
00:10:37,960 --> 00:10:41,080
since it's egress traffic for specific region,

193
00:10:41,080 --> 00:10:45,280
you're also having a lot of extra costs probably,

194
00:10:45,280 --> 00:10:48,320
depending on your volume of data traffic.

195
00:10:48,320 --> 00:10:54,000
- Yeah, one of your favorite topics is Azure Virtual Network

196
00:10:54,000 --> 00:10:57,560
and Manager for listeners, I'm similar with it.

197
00:10:57,560 --> 00:11:01,960
What problem do is itself and why has Microsoft created?

198
00:11:01,960 --> 00:11:08,160
- Well, why they exactly created it?

199
00:11:08,160 --> 00:11:09,440
Then I don't know of course.

200
00:11:09,440 --> 00:11:16,320
But it solves quite a few problems to be honest.

201
00:11:16,320 --> 00:11:20,480
And it's also a resource that is not used

202
00:11:20,480 --> 00:11:22,760
in my opinion enough at the moment.

203
00:11:23,760 --> 00:11:26,920
But it does a couple of things.

204
00:11:26,920 --> 00:11:33,200
On the one hand, it has IPAM in it,

205
00:11:33,200 --> 00:11:35,240
so IP address management.

206
00:11:35,240 --> 00:11:40,200
So what you can do, and especially when you have multiple,

207
00:11:40,200 --> 00:11:44,360
branches, multiple networks,

208
00:11:44,360 --> 00:11:48,040
you can put all your network ranges in your IPAM.

209
00:11:48,040 --> 00:11:52,560
And from there you can assign the ranges towards networks.

210
00:11:52,560 --> 00:11:54,600
And you will always know which networks are in use,

211
00:11:54,600 --> 00:11:57,040
how many IP addresses you have in use,

212
00:11:57,040 --> 00:11:59,520
more importantly, how many IP addresses you have free.

213
00:11:59,520 --> 00:12:03,400
And the great thing of IPAM is you can also put your

214
00:12:03,400 --> 00:12:05,560
on-premise networks in there

215
00:12:05,560 --> 00:12:09,400
and just give them a fact that I cannot be assigned in Azure,

216
00:12:09,400 --> 00:12:11,600
or actually you get some nice troubles.

217
00:12:11,600 --> 00:12:15,920
But yeah, it makes it one pane of glass basically

218
00:12:15,920 --> 00:12:20,280
to see which networks are in use and how many addresses you use.

219
00:12:21,080 --> 00:12:25,400
And another thing it does is it helps you setting up connectivity

220
00:12:25,400 --> 00:12:27,200
between your networks.

221
00:12:27,200 --> 00:12:29,880
So you can make a star network if you want.

222
00:12:29,880 --> 00:12:33,160
You can make HubSpoke set up if you want,

223
00:12:33,160 --> 00:12:36,440
just with one set up.

224
00:12:36,440 --> 00:12:39,960
And then when you add new networks to your environment,

225
00:12:39,960 --> 00:12:41,920
you can just give them a tag.

226
00:12:41,920 --> 00:12:44,480
And then when the first, you will network manage,

227
00:12:44,480 --> 00:12:46,440
it sees that tag on a network.

228
00:12:46,440 --> 00:12:50,120
It will automatically load it into the HubSpoke,

229
00:12:50,120 --> 00:12:53,160
for example, and set up all the routing

230
00:12:53,160 --> 00:12:55,160
so everything works as expected.

231
00:12:55,160 --> 00:13:00,280
Another great thing that is in virtual network manager

232
00:13:00,280 --> 00:13:02,840
is another security feature.

233
00:13:02,840 --> 00:13:05,480
We mentioned the network security groups.

234
00:13:05,480 --> 00:13:10,360
So if you know network security groups,

235
00:13:10,360 --> 00:13:14,200
that's basically, well, let's say IP tables in Linux,

236
00:13:14,200 --> 00:13:18,200
you set up some rules, they work from top to bottom.

237
00:13:19,120 --> 00:13:22,960
So everything you open up at the top and get sparse

238
00:13:22,960 --> 00:13:25,000
through until you block everything at the bottom.

239
00:13:25,000 --> 00:13:27,200
And then you set to go.

240
00:13:27,200 --> 00:13:31,720
But if you have a lot of networks with a lot of network security groups

241
00:13:31,720 --> 00:13:34,960
and there is a problem, you might not want to go

242
00:13:34,960 --> 00:13:38,120
through all network security groups to open up a specific portal

243
00:13:38,120 --> 00:13:39,880
to test something.

244
00:13:39,880 --> 00:13:42,960
And with Azure Virtual Network Manager,

245
00:13:42,960 --> 00:13:46,760
you have basically an admin rule

246
00:13:46,760 --> 00:13:50,080
that you can push towards all network security groups

247
00:13:50,080 --> 00:13:52,560
that are connected to the Azure Virtual Network Manager.

248
00:13:52,560 --> 00:13:56,920
And every rule that you put in there gets preference

249
00:13:56,920 --> 00:14:01,840
over all the rules in your standard network security groups.

250
00:14:01,840 --> 00:14:05,320
So if you want to open up a portal for three, for example,

251
00:14:05,320 --> 00:14:08,840
towards everything in all your networks,

252
00:14:08,840 --> 00:14:11,440
you just make one rule and automatically

253
00:14:11,440 --> 00:14:13,920
gets placed in front of the energy.

254
00:14:15,040 --> 00:14:16,840
So basically when you have an energy,

255
00:14:16,840 --> 00:14:20,760
you give an order to it, you're just starting with 100,

256
00:14:20,760 --> 00:14:25,760
up to 55,535, if I say it correctly.

257
00:14:25,760 --> 00:14:30,440
And basically what the admin rule does is make it

258
00:14:30,440 --> 00:14:34,240
basically from one till 99.

259
00:14:34,240 --> 00:14:36,720
So it really gets put in front of it.

260
00:14:36,720 --> 00:14:40,880
So the rule that you put in there always allowed

261
00:14:40,880 --> 00:14:43,240
or denied if you want that, it's also an option.

262
00:14:44,240 --> 00:14:48,760
And the third thing that it basically does is routing.

263
00:14:48,760 --> 00:14:53,720
So basically when you set up a HUBSPOKE network

264
00:14:53,720 --> 00:14:56,200
at this moment, you always have to create UDRs,

265
00:14:56,200 --> 00:14:59,120
use the defined routes to root all the traffic

266
00:14:59,120 --> 00:15:01,960
from your spokes towards a firewall

267
00:15:01,960 --> 00:15:06,960
or whatever you have in your hub to send the traffic

268
00:15:06,960 --> 00:15:08,880
towards the internet.

269
00:15:11,960 --> 00:15:13,960
Of course mistakes are easily made.

270
00:15:13,960 --> 00:15:18,960
If you do these things, am I using the routing options

271
00:15:18,960 --> 00:15:21,640
from Azure Quits on network manager,

272
00:15:21,640 --> 00:15:24,040
you can all go it from one place.

273
00:15:24,040 --> 00:15:26,480
So you basically just have to maintain one root table

274
00:15:26,480 --> 00:15:29,080
and you can push that towards all networks if you want.

275
00:15:29,080 --> 00:15:34,120
- Okay, I think a little bit for people.

276
00:15:34,120 --> 00:15:40,520
Normally the people love to have a big one big link

277
00:15:40,520 --> 00:15:44,160
in network, one big Facebook network.

278
00:15:44,160 --> 00:15:49,160
Why companies should have more networks

279
00:15:49,160 --> 00:15:52,680
than one big, ultimate network?

280
00:15:52,680 --> 00:15:57,920
- That's kind of a trick question.

281
00:15:57,920 --> 00:16:07,720
Well, you should have smaller networks in Azure

282
00:16:09,080 --> 00:16:11,680
is basically just because people are stupid

283
00:16:11,680 --> 00:16:13,720
and it's for people to understand.

284
00:16:13,720 --> 00:16:19,480
Because like I said before, everything in Azure,

285
00:16:19,480 --> 00:16:22,680
especially if you're spearing in those kind of things,

286
00:16:22,680 --> 00:16:24,560
it becomes one big network

287
00:16:24,560 --> 00:16:30,040
and because all the routing is done at your virtual machines

288
00:16:30,040 --> 00:16:31,880
or at your platform service,

289
00:16:31,880 --> 00:16:37,160
yeah, if you have one, it doesn't small network

290
00:16:37,160 --> 00:16:39,920
of one big network, if you pair them together,

291
00:16:39,920 --> 00:16:40,960
it's still one network.

292
00:16:40,960 --> 00:16:43,480
So for Azure, it really doesn't matter

293
00:16:43,480 --> 00:16:45,360
because it's one network anyway.

294
00:16:45,360 --> 00:16:49,800
And that's why your network security groups are so important.

295
00:16:49,800 --> 00:16:52,120
Because a lot of people say,

296
00:16:52,120 --> 00:16:58,120
well, we run Azure Firewall so we don't need network security groups

297
00:16:58,120 --> 00:17:02,240
but because it's one big network underneath,

298
00:17:02,240 --> 00:17:04,640
they tend to get about that

299
00:17:04,640 --> 00:17:08,040
and that's why your network security groups are so important

300
00:17:08,040 --> 00:17:10,920
because if you make one mistake in your routing,

301
00:17:10,920 --> 00:17:15,120
then the different machines can still talk to each other.

302
00:17:15,120 --> 00:17:20,200
And that's not always desired.

303
00:17:20,200 --> 00:17:24,600
- When we talk about network security,

304
00:17:24,600 --> 00:17:26,920
what are security admin rules?

305
00:17:26,920 --> 00:17:31,640
- Security admin rules, those are the things

306
00:17:31,640 --> 00:17:34,520
I just mentioned from the Azure Virtual Network Manager.

307
00:17:34,520 --> 00:17:36,880
So basically those are the rules

308
00:17:36,880 --> 00:17:40,120
that you can put in front of the rules in a network security group.

309
00:17:40,120 --> 00:17:44,480
And basically what they have three options,

310
00:17:44,480 --> 00:17:47,520
they have an allow, they have a deny.

311
00:17:47,520 --> 00:17:52,760
And I can't remember how to exactly call the third option

312
00:17:52,760 --> 00:17:56,480
but the third option is just put it in there

313
00:17:56,480 --> 00:17:59,800
and even though if it's allowed and it gets blocked

314
00:17:59,800 --> 00:18:02,600
in the NSG later on, then block the traffic.

315
00:18:03,560 --> 00:18:08,560
So you can make it a normal security rule basically

316
00:18:08,560 --> 00:18:12,520
where you can really override the NSG rules

317
00:18:12,520 --> 00:18:15,320
so that your traffic is always allowed.

318
00:18:15,320 --> 00:18:20,320
- Can I work on Azure Virtual Network Manager

319
00:18:20,320 --> 00:18:23,640
or in the network security groups?

320
00:18:23,640 --> 00:18:27,200
Can I also use their bicep to set up?

321
00:18:27,200 --> 00:18:29,320
- Yes, luckily.

322
00:18:31,840 --> 00:18:34,800
Now definitely everything that's in,

323
00:18:34,800 --> 00:18:38,360
so the Azure Virtual Network Manager

324
00:18:38,360 --> 00:18:40,600
is a separate resource that you can set up

325
00:18:40,600 --> 00:18:43,720
and down the, you have the IPAM,

326
00:18:43,720 --> 00:18:45,240
you have the connectivity, the security,

327
00:18:45,240 --> 00:18:46,840
and routing settings.

328
00:18:46,840 --> 00:18:50,880
And each of them can be set up with bicep.

329
00:18:50,880 --> 00:18:55,400
Everything you can set up at infrastructure as code,

330
00:18:55,400 --> 00:18:59,760
do your tests around it, use what if deployments

331
00:18:59,760 --> 00:19:02,960
to see if it does what if it's gonna deploy,

332
00:19:02,960 --> 00:19:05,280
what you think is gonna deploy.

333
00:19:05,280 --> 00:19:08,240
So yeah, that's all taken care of and it works perfectly.

334
00:19:08,240 --> 00:19:11,920
- I think also one topic is,

335
00:19:11,920 --> 00:19:14,600
we have to speak about Azure landing zones.

336
00:19:14,600 --> 00:19:17,760
Can you tell us a little bit about what is it

337
00:19:17,760 --> 00:19:22,760
and how well is it integrated in the Azure Virtual

338
00:19:22,760 --> 00:19:26,960
Network Manager?

339
00:19:29,160 --> 00:19:31,880
Well, landing zones by themselves,

340
00:19:31,880 --> 00:19:32,880
let's start by the beginning,

341
00:19:32,880 --> 00:19:34,480
what are landing zones are on this indeed.

342
00:19:34,480 --> 00:19:40,040
Basically, if you look,

343
00:19:40,040 --> 00:19:43,480
let's take the Hubspoke model as an example here.

344
00:19:43,480 --> 00:19:47,920
So if you look at the Azure Well Architected Framework,

345
00:19:47,920 --> 00:19:51,880
if you have a rainy Sunday afternoon,

346
00:19:51,880 --> 00:19:56,880
look it up and read through the Azure Architectural pages,

347
00:19:56,880 --> 00:19:58,840
it's gonna take a couple of days.

348
00:19:59,680 --> 00:20:04,000
- But basically, if you have your setup,

349
00:20:04,000 --> 00:20:07,640
you have your hub, that's why you basically have all your

350
00:20:07,640 --> 00:20:11,240
connectivity, your routing, your firewall,

351
00:20:11,240 --> 00:20:15,000
everything that makes up the basic platform basically.

352
00:20:15,000 --> 00:20:18,120
And then for the spokes,

353
00:20:18,120 --> 00:20:22,400
what Len, and not a word for the spokes,

354
00:20:22,400 --> 00:20:26,320
it's either landing zone or workload.

355
00:20:26,320 --> 00:20:28,360
So basically if you have a specific workload,

356
00:20:28,360 --> 00:20:31,280
so for example, if you have something,

357
00:20:31,280 --> 00:20:35,520
some web application, you'll put that in a different spoke,

358
00:20:35,520 --> 00:20:38,680
you could put your database in a different spoke,

359
00:20:38,680 --> 00:20:40,720
you could have different departments

360
00:20:40,720 --> 00:20:45,040
having different landings on those at different spokes.

361
00:20:45,040 --> 00:20:47,800
That kind of depends on the setup of the company,

362
00:20:47,800 --> 00:20:49,960
how you setup your spokes.

363
00:20:49,960 --> 00:20:54,960
Basically, a landing zone or a spoke is closed off

364
00:20:55,120 --> 00:20:59,080
and environment which does a certain job,

365
00:20:59,080 --> 00:21:01,280
depending on what it is.

366
00:21:01,280 --> 00:21:04,600
And from there, all the traffic goes towards the hub

367
00:21:04,600 --> 00:21:07,560
to your firewall or to your outgoing device.

368
00:21:07,560 --> 00:21:10,040
Could be a natural firewall, could be a not gateway,

369
00:21:10,040 --> 00:21:12,800
could be a virtual network appliance,

370
00:21:12,800 --> 00:21:16,600
like Cisco, 14th, whatever you're using.

371
00:21:16,600 --> 00:21:21,480
But it's a self-contained piece of networking basically.

372
00:21:22,800 --> 00:21:26,960
When Microsoft came to you and say, hey, Rex,

373
00:21:26,960 --> 00:21:29,920
we give you all the manpower, all the money you need,

374
00:21:29,920 --> 00:21:34,280
what feature will you develop for the Azure Virtual Network Manager?

375
00:21:34,280 --> 00:21:49,000
Not so much a feature, but more some clarifications.

376
00:21:51,080 --> 00:21:54,520
And for example, you have connectivity.

377
00:21:54,520 --> 00:22:01,680
And you can set up a mass network or a Huppenspoke network,

378
00:22:01,680 --> 00:22:05,480
automatically from Azure Virtual Network Manager.

379
00:22:05,480 --> 00:22:09,520
But the problem is you can only have one active

380
00:22:09,520 --> 00:22:12,600
at a certain VNet at a time, which makes sense, of course.

381
00:22:12,600 --> 00:22:17,560
But if one is already deployed,

382
00:22:18,720 --> 00:22:21,640
and you're gonna deploy it again or another one,

383
00:22:21,640 --> 00:22:24,600
it doesn't say it's already connected to something.

384
00:22:24,600 --> 00:22:28,520
So basically, I would just build in some extra

385
00:22:28,520 --> 00:22:34,840
reporting tools basically to show how to set up a set of moments.

386
00:22:34,840 --> 00:22:37,320
And if something is already set up in a specific way,

387
00:22:37,320 --> 00:22:41,400
then you first get a warning before overriding it, for example.

388
00:22:41,400 --> 00:22:45,120
Yeah, the more there's a moderate network resource of that,

389
00:22:45,120 --> 00:22:46,520
you get to get to get to the point by the way.

390
00:22:46,520 --> 00:22:48,880
But that's not actual, the network manager.

391
00:22:48,880 --> 00:22:54,200
Infrastructure as a code is actually, I think,

392
00:22:54,200 --> 00:22:58,520
yeah, it's gone from my staff to essential.

393
00:22:58,520 --> 00:23:01,440
Why is this actually sort of a hot topic?

394
00:23:01,440 --> 00:23:08,400
Well, I don't, yeah, what is it a hot topic?

395
00:23:08,400 --> 00:23:11,880
It's basically on everybody's mind for you.

396
00:23:11,880 --> 00:23:14,600
Well, it should be on everybody's mind for years, of course.

397
00:23:15,440 --> 00:23:19,600
And that's basically because of that nice word

398
00:23:19,600 --> 00:23:26,360
that somebody invite invented omnipotent set up.

399
00:23:26,360 --> 00:23:31,960
So basically when you set up a landing zone in one location,

400
00:23:31,960 --> 00:23:36,680
and you want to do that again or in another region

401
00:23:36,680 --> 00:23:39,560
or for another customer, you always want them

402
00:23:39,560 --> 00:23:40,960
to look exactly the same.

403
00:23:42,240 --> 00:23:46,480
And like I said before, a lot of people are stupid.

404
00:23:46,480 --> 00:23:50,360
And it's difficult to do things the same every time.

405
00:23:50,360 --> 00:23:53,000
Also, people are lazy and don't want to do that.

406
00:23:53,000 --> 00:23:57,640
So if you set it up in infrastructure as code

407
00:23:57,640 --> 00:23:59,400
that it has multiple advantages,

408
00:23:59,400 --> 00:24:03,320
it will always set things up always in the same way

409
00:24:03,320 --> 00:24:04,440
that you want it.

410
00:24:04,440 --> 00:24:10,600
Another thing is that you can do the one every deployments.

411
00:24:10,600 --> 00:24:13,080
So you can really check what is going to be deployed

412
00:24:13,080 --> 00:24:17,560
and is that still the same thing that I intended to deploy.

413
00:24:17,560 --> 00:24:21,800
And another thing, if your code is set up correctly,

414
00:24:21,800 --> 00:24:26,400
and you got your pipelines and your runs in order,

415
00:24:26,400 --> 00:24:29,640
you can also use PESTA for example to do some tests

416
00:24:29,640 --> 00:24:32,800
to make sure that all your code is up to date

417
00:24:32,800 --> 00:24:37,240
that all parameters are filled with things that you want

418
00:24:37,240 --> 00:24:39,520
before really going into Azure

419
00:24:39,520 --> 00:24:43,360
and perhaps being blocked by a policy that you set up

420
00:24:43,360 --> 00:24:45,840
or all those kind of things.

421
00:24:45,840 --> 00:24:55,720
When did you first start using infrastructure as a code?

422
00:24:55,720 --> 00:25:03,800
When did I put, I think,

423
00:25:07,160 --> 00:25:12,640
I think that was in my Amazon days already, so 2012, 2013.

424
00:25:12,640 --> 00:25:18,120
I can't remember what we used back then to be honest.

425
00:25:18,120 --> 00:25:22,600
I think it was not a good idea anymore.

426
00:25:22,600 --> 00:25:28,120
We started with, especially for the Windows Azure Pack,

427
00:25:28,120 --> 00:25:33,320
for example, in World Power Show with DSC Design Stage

428
00:25:33,320 --> 00:25:38,320
and configuration. And nowadays, in my case,

429
00:25:38,320 --> 00:25:42,520
because there are multiple things that you can do of course.

430
00:25:42,520 --> 00:25:47,520
But for me, I work with PowerShell, Azure GLI, BICEB,

431
00:25:47,520 --> 00:25:50,520
and Azure FIRT to have fair-fright modules.

432
00:25:50,520 --> 00:25:59,360
- Yeah, you say, Amazon, so you cannot use BICEB,

433
00:25:59,360 --> 00:26:01,040
so I think so. - No.

434
00:26:02,000 --> 00:26:04,520
- It is here, I don't know, it's Terraform.

435
00:26:04,520 --> 00:26:09,520
But how to choose BICEB Terraform on templates?

436
00:26:09,520 --> 00:26:11,840
When is what the right tool?

437
00:26:11,840 --> 00:26:15,960
- Well, eventually environment, of course,

438
00:26:15,960 --> 00:26:19,720
like, certainly, Amazon, you can use BICEBs,

439
00:26:19,720 --> 00:26:22,600
so you would probably use Terraform,

440
00:26:22,600 --> 00:26:26,880
but it's also what you use to use.

441
00:26:26,880 --> 00:26:30,720
So I'm using, coming from Microsoft World,

442
00:26:30,720 --> 00:26:34,800
basically for the last 12, 13 years now.

443
00:26:34,800 --> 00:26:40,560
For me, what we started with, with ArmTem place,

444
00:26:40,560 --> 00:26:42,960
because that first was the only thing

445
00:26:42,960 --> 00:26:45,200
that was there for deployments.

446
00:26:45,200 --> 00:26:49,960
And then luckily, they came with a more readable language

447
00:26:49,960 --> 00:26:52,240
at BICEB for deployments.

448
00:26:52,240 --> 00:26:58,480
So for me, that was a logical step to move on to BICEB.

449
00:26:59,920 --> 00:27:02,240
I know there are a lot of people that use Terraform,

450
00:27:02,240 --> 00:27:04,680
also for deployments towards Azure.

451
00:27:04,680 --> 00:27:10,560
Yeah, for me, it was just the logical choice

452
00:27:10,560 --> 00:27:11,800
to go to BICEB.

453
00:27:11,800 --> 00:27:16,360
There's really no right or wrong in this.

454
00:27:16,360 --> 00:27:19,080
It's just use the tool that you need,

455
00:27:19,080 --> 00:27:22,000
not the tool that somebody wants you to use.

456
00:27:22,000 --> 00:27:29,520
- Where there was this picture fits the Azure Merify

457
00:27:29,520 --> 00:27:30,680
and the modules in...

458
00:27:30,680 --> 00:27:36,040
Well, the Azure Fairfile modules are basically

459
00:27:36,040 --> 00:27:37,600
a set of BICEB modules.

460
00:27:37,600 --> 00:27:43,840
They are developed in the basic bi-meject Tracy for Microsoft.

461
00:27:43,840 --> 00:27:50,520
And it's just, yeah, comprehensive set of modules

462
00:27:50,520 --> 00:27:55,080
which touch not 100% of all Azure resources yet,

463
00:27:55,080 --> 00:27:56,560
but quite a lot of them.

464
00:27:58,520 --> 00:28:03,520
And they get a very reasonable skill.

465
00:28:03,520 --> 00:28:11,760
It's also open source, so you can make your own PRs to it.

466
00:28:11,760 --> 00:28:13,720
I've also done that a couple of times.

467
00:28:13,720 --> 00:28:19,440
So if you're missing something that is offered by Microsoft,

468
00:28:19,440 --> 00:28:22,960
by the port, also show you know there are options

469
00:28:22,960 --> 00:28:28,000
and you can find all the documentation in Microsoft Learn, of course.

470
00:28:28,000 --> 00:28:33,000
But if you see that it's missing in the Azure Fairfile modules,

471
00:28:33,000 --> 00:28:37,440
you can just add it, create a PR and then it will get implemented.

472
00:28:37,440 --> 00:28:41,360
For example, I had something last year

473
00:28:41,360 --> 00:28:45,400
which was for a virtual network gateway

474
00:28:45,400 --> 00:28:50,400
and it was kind of an niche thing that nobody used a lot,

475
00:28:50,400 --> 00:28:53,120
but which I needed for specific customer.

476
00:28:54,400 --> 00:28:58,120
They didn't work correctly in the EM modules.

477
00:28:58,120 --> 00:29:02,080
So we created a fix for it and it's now part of the modules.

478
00:29:02,080 --> 00:29:05,440
So that's also nice to see your own code now

479
00:29:05,440 --> 00:29:09,760
and being used by everybody that uses that specific functionality.

480
00:29:09,760 --> 00:29:16,720
- When I handle my projects, I normally use dev ops, okay.

481
00:29:16,720 --> 00:29:18,440
I'm an old guy.

482
00:29:18,440 --> 00:29:20,040
(laughs)

483
00:29:20,040 --> 00:29:21,040
- Thank you.

484
00:29:21,040 --> 00:29:24,360
- So I'm on, yeah.

485
00:29:24,520 --> 00:29:30,520
Treat me to use Git, but how do you organize

486
00:29:30,520 --> 00:29:34,160
a large infrastructure as code projects?

487
00:29:34,160 --> 00:29:41,520
- Well, we always use, always mostly use Azure dev ops still

488
00:29:41,520 --> 00:29:45,600
and that's not because Git ops is not good

489
00:29:45,600 --> 00:29:50,080
because Git ops is definitely perfect for it.

490
00:29:50,080 --> 00:29:54,000
But the main advantage of Azure dev ops is that

491
00:29:54,000 --> 00:29:57,240
you also have the boards in there

492
00:29:57,240 --> 00:30:00,880
and which is not as good yet in GitHub.

493
00:30:00,880 --> 00:30:02,600
So you have everything in one place.

494
00:30:02,600 --> 00:30:08,520
But yeah, we definitely always use some kind of source control system

495
00:30:08,520 --> 00:30:12,680
whether it's Azure dev ops or GitHub in our case.

496
00:30:12,680 --> 00:30:14,920
Then there are more of course like GitLab

497
00:30:14,920 --> 00:30:17,880
or BitBook that are those kinds of things.

498
00:30:17,880 --> 00:30:19,800
We don't use them, but...

499
00:30:19,800 --> 00:30:22,360
- So for us, it's mostly Azure dev ops.

500
00:30:23,360 --> 00:30:27,560
And when we think of,

501
00:30:27,560 --> 00:30:29,600
when would you say

502
00:30:29,600 --> 00:30:35,000
every networking should always deploy through code?

503
00:30:35,000 --> 00:30:47,440
- I would say so, although it's not always possible.

504
00:30:47,440 --> 00:30:52,080
For example, if you deploy a data press,

505
00:30:52,080 --> 00:30:54,360
it will deploy some things on the planet's own.

506
00:30:54,360 --> 00:30:56,040
So you have no control over there.

507
00:30:56,040 --> 00:31:01,680
But basically, well, not only networking, by the way,

508
00:31:01,680 --> 00:31:04,880
you deploy everything via code.

509
00:31:04,880 --> 00:31:11,360
And of course, that has the main advantage is that

510
00:31:11,360 --> 00:31:13,160
if you have to redeploy it again,

511
00:31:13,160 --> 00:31:15,200
you can deploy it in the same way.

512
00:31:15,200 --> 00:31:19,040
But also, if for some reason you break something

513
00:31:21,880 --> 00:31:24,600
on your environment, on the one hand,

514
00:31:24,600 --> 00:31:26,280
you can restore backup of course,

515
00:31:26,280 --> 00:31:28,960
but that doesn't always have all the settings

516
00:31:28,960 --> 00:31:31,360
for a virtual machine, for example, or...

517
00:31:31,360 --> 00:31:35,880
And especially for your network settings,

518
00:31:35,880 --> 00:31:37,280
well, you can backup those,

519
00:31:37,280 --> 00:31:39,600
so you need to have those in code.

520
00:31:39,600 --> 00:31:40,960
And if you have one network,

521
00:31:40,960 --> 00:31:43,880
well, you can get away with it to use clickups

522
00:31:43,880 --> 00:31:46,480
and create a manually.

523
00:31:46,480 --> 00:31:50,240
But if you have to create 300 of them, for example,

524
00:31:50,240 --> 00:31:53,360
have fun, you don't want to do that by hand.

525
00:31:53,360 --> 00:32:00,720
And how can we, or how do you balance flexibility

526
00:32:00,720 --> 00:32:02,440
with standardization?

527
00:32:02,440 --> 00:32:07,880
That's always difficult.

528
00:32:07,880 --> 00:32:17,720
But, yeah, as long as if you set up your infrastructure

529
00:32:17,720 --> 00:32:21,600
and manage code, well, I will say correctly,

530
00:32:21,600 --> 00:32:24,320
but if you keep your standards there,

531
00:32:24,320 --> 00:32:29,320
and work with parameters where needed,

532
00:32:29,320 --> 00:32:32,640
you get a lot of flexibility even in your default code.

533
00:32:32,640 --> 00:32:39,960
- When we think a little bit about the new trends,

534
00:32:39,960 --> 00:32:43,120
co-pilots everywhere, can AI help

535
00:32:43,120 --> 00:32:45,760
develop us right better infrastructure as code?

536
00:32:47,120 --> 00:32:51,000
It can definitely help as long as the focus is on help.

537
00:32:51,000 --> 00:32:59,120
Now, it can definitely help, especially if you know what you're doing.

538
00:32:59,120 --> 00:33:02,600
It saves you a lot of time because you don't have to type in everything yourself.

539
00:33:02,600 --> 00:33:09,240
It becomes a problem when you're not exactly...

540
00:33:09,240 --> 00:33:11,640
If you don't exactly know what you're doing,

541
00:33:11,640 --> 00:33:13,240
and when it generates code,

542
00:33:13,240 --> 00:33:15,120
and you have no idea what it's doing.

543
00:33:16,720 --> 00:33:21,720
I've seen people have creating stuff with co-pilot

544
00:33:21,720 --> 00:33:24,720
to create a script to do something

545
00:33:24,720 --> 00:33:26,720
because something was not working.

546
00:33:26,720 --> 00:33:29,720
And they didn't check the script that was created,

547
00:33:29,720 --> 00:33:32,720
and then it was by domain controller.

548
00:33:32,720 --> 00:33:36,720
So, it's definitely a tool.

549
00:33:36,720 --> 00:33:41,720
If you're able to definitely use it because it saves you a lot of time,

550
00:33:41,720 --> 00:33:45,720
but you always check what it's generating.

551
00:33:45,720 --> 00:33:52,720
And, yeah, did you see some common mistakes new comers make

552
00:33:52,720 --> 00:33:55,720
in infrastructure as a code?

553
00:33:55,720 --> 00:34:08,720
Yeah, well, the most things that I see is that people do not create network security groups.

554
00:34:10,720 --> 00:34:15,720
Just believing that it's a close-off environment.

555
00:34:15,720 --> 00:34:20,720
So, we don't need them between our different networks because,

556
00:34:20,720 --> 00:34:24,720
yeah, well, we have a firewall in place, so we don't need that.

557
00:34:24,720 --> 00:34:31,720
And, yeah, that's something that's not necessarily a big problem,

558
00:34:31,720 --> 00:34:36,720
but it can become a big problem if somebody finds some way into your network.

559
00:34:36,720 --> 00:34:43,720
And then, yeah, they have access to everything in one go.

560
00:34:43,720 --> 00:34:51,720
I see one of your talking topics of really fascinating question.

561
00:34:51,720 --> 00:34:54,720
Can error function actually be secure?

562
00:34:54,720 --> 00:34:56,720
Let's start here.

563
00:34:56,720 --> 00:35:00,720
Why do people worry about error functions?

564
00:35:00,720 --> 00:35:02,720
Well, it is not only as a function,

565
00:35:02,720 --> 00:35:05,720
but also web applications.

566
00:35:05,720 --> 00:35:14,720
I just use Azure Functions in my talks because it's easier for me to create an Azure Function with some functionality as an Azure Web App.

567
00:35:14,720 --> 00:35:17,720
But that's just me.

568
00:35:17,720 --> 00:35:22,720
But the same difference counts for both.

569
00:35:22,720 --> 00:35:28,720
But, of course, an Azure Function can be used to directly talk to machines inside your network

570
00:35:28,720 --> 00:35:34,720
to get data from inside your network and send that somewhere.

571
00:35:34,720 --> 00:35:40,720
And because it just fire and forget basically, you throw something in there,

572
00:35:40,720 --> 00:35:45,720
it does something and it spits some answer out.

573
00:35:45,720 --> 00:35:50,720
And you have no idea what happened in the back and where it went.

574
00:35:50,720 --> 00:35:57,720
And, and who's calling the function, for example.

575
00:35:57,720 --> 00:36:01,720
And another thing with Azure Functions, for example.

576
00:36:01,720 --> 00:36:09,720
If you have to get information from a third party, they often do IP-wide listing.

577
00:36:09,720 --> 00:36:21,720
And by default, I think there are 25 or 30 addresses that are used for outgoing traffic from a function app from the web app.

578
00:36:21,720 --> 00:36:31,720
And not all third parties want to open up all those 30 IP addresses to make to be sure that your function will work correctly.

579
00:36:31,720 --> 00:36:41,720
So if you use VNet integration with your virtual network, you can route all that traffic via a not gateway, for example,

580
00:36:41,720 --> 00:36:48,720
so that it always goes out with the same IP address, which makes IP-wide listing a lot easier.

581
00:36:48,720 --> 00:37:01,720
And another thing that you can do, and which you might want to do anyway, is if you do VNet integration and you send your traffic not towards not gateway or to watch a firewall,

582
00:37:01,720 --> 00:37:09,720
you can also monitor the traffic that is outgoing from your function app or your website in the firewall locks.

583
00:37:09,720 --> 00:37:15,720
And you have to really open up the different IP addresses that it can talk to.

584
00:37:15,720 --> 00:37:22,720
And then you have to really multi-level security in some simple goes and the same is for the incoming traffic.

585
00:37:22,720 --> 00:37:27,720
Basically, normally, all traffic comes in directly from the internet.

586
00:37:27,720 --> 00:37:36,720
That's not something that you want. So if you set it up with private endpoints, you close it off completely from from the internet.

587
00:37:36,720 --> 00:37:39,720
So it's completely internally.

588
00:37:39,720 --> 00:38:01,720
You can reach it from within your network, you can reach it from your connected network, you can even reach it from outblast from a virtual, but if you use VNet integration from there, but you can still put, for example, from or an application gateway in front of it, to make it reachable from the internet if you want.

589
00:38:01,720 --> 00:38:07,720
But by using a different device, you also minimize your text service.

590
00:38:07,720 --> 00:38:14,720
And then you can also use multiple advantages to put network security in place for your free Azure function.

591
00:38:14,720 --> 00:38:18,720
I think the security topic is really interesting.

592
00:38:18,720 --> 00:38:33,720
What are the, yeah, I see what are the most, what mistakes that you see in most often when it's kind of Azure function.

593
00:38:33,720 --> 00:38:40,720
Basically, that there is no security at all.

594
00:38:40,720 --> 00:38:54,720
And as a function is like is that basically a web application, but for a web application, you have some security options that you can put in place like out and those kinds of things.

595
00:38:54,720 --> 00:38:57,720
You don't have that for Azure functions.

596
00:38:57,720 --> 00:39:03,720
And that's why it's also a great subject to work with in this case.

597
00:39:03,720 --> 00:39:07,720
What you can do with Azure function is assign keys.

598
00:39:07,720 --> 00:39:18,720
So if you have a key or token that you can pass as a parameter parameter sorry to kick off the function.

599
00:39:18,720 --> 00:39:25,720
And as soon as that parameter gets out, then everybody still knows it.

600
00:39:25,720 --> 00:39:33,720
So that's not really a decent way of doing things in my opinion.

601
00:39:33,720 --> 00:39:39,720
So basically it's just everybody just makes them available for everybody.

602
00:39:39,720 --> 00:39:46,720
And of course, you do have some some network furniture you can block on IP addresses.

603
00:39:46,720 --> 00:39:52,720
Yeah, that's not always the best way to go.

604
00:39:52,720 --> 00:39:58,720
I think another topic when we talk about security is it's authentic, authentication.

605
00:39:58,720 --> 00:40:06,720
How should developers think about it?

606
00:40:06,720 --> 00:40:16,720
Well, that again depends on the type of service that you offer.

607
00:40:16,720 --> 00:40:24,720
For some it is enough to just set all out and have them authenticate against your.

608
00:40:24,720 --> 00:40:28,720
Entra tenant for example.

609
00:40:28,720 --> 00:40:31,720
But it could also be.

610
00:40:31,720 --> 00:40:36,720
And it uses an internal database, for example, of user accounts.

611
00:40:36,720 --> 00:40:45,720
So there are different ways, but if you can use an old out flavor, let's say it like that.

612
00:40:45,720 --> 00:40:50,720
I think that's one of the best ways at this moment.

613
00:40:50,720 --> 00:40:58,720
Please do not use basic authentication anymore if that's still an option.

614
00:40:58,720 --> 00:41:06,720
And I think, yeah, we're a little bit played in this often.

615
00:41:06,720 --> 00:41:08,720
I hear often it's managed identity.

616
00:41:08,720 --> 00:41:09,720
What is it?

617
00:41:09,720 --> 00:41:10,720
What is it?

618
00:41:10,720 --> 00:41:15,720
And what role does it play?

619
00:41:15,720 --> 00:41:18,720
Not sure how I.

620
00:41:18,720 --> 00:41:22,720
Basically, a managed identity is what it says that it is.

621
00:41:22,720 --> 00:41:26,720
It's an identity that is either managed by Microsoft.

622
00:41:26,720 --> 00:41:28,720
So a system and identity.

623
00:41:28,720 --> 00:41:30,720
Or you have use a managed identities.

624
00:41:30,720 --> 00:41:37,720
And in that case, you set a secret on it yourself and do some things with it.

625
00:41:37,720 --> 00:41:44,720
But basically what it is, it gives for example, a virtual machine or another resources that they're in key roles.

626
00:41:44,720 --> 00:41:48,720
They're in, they're in all kinds of resources nowadays and Azure.

627
00:41:48,720 --> 00:41:53,720
But basically it gives it the option.

628
00:41:53,720 --> 00:42:02,720
To have that, for example, a virtual machine, if you give that a managed identity, you can give that managed identity.

629
00:42:02,720 --> 00:42:07,720
For example, reading rights on a key vault or on a secret in a key vault.

630
00:42:07,720 --> 00:42:12,720
For that from that virtual machine, it can read a secret.

631
00:42:12,720 --> 00:42:17,720
And otherwise you would have to set it up with user authentication or.

632
00:42:17,720 --> 00:42:23,720
And then you would have to set it up with a key vault.

633
00:42:23,720 --> 00:42:27,720
And then you would have to set it up with a key vault.

634
00:42:27,720 --> 00:42:31,720
And then you would have to set it up with a key vault.

635
00:42:31,720 --> 00:42:35,720
And then you would have to set it up with a key vault.

636
00:42:35,720 --> 00:42:38,720
And then you would have to set it up with a key vault.

637
00:42:38,720 --> 00:42:41,720
And then you would have to set it up with a key vault.

638
00:42:41,720 --> 00:42:44,720
And then you would have to set it up with a key vault.

639
00:42:44,720 --> 00:42:47,720
And then you would have to set it up with a key vault.

640
00:42:47,720 --> 00:42:50,720
And then you would have to set it up with a key vault.

641
00:42:50,720 --> 00:42:53,720
And then you would have to set it up with a key vault.

642
00:42:53,720 --> 00:42:56,720
And then you would have to set it up with a key vault.

643
00:42:56,720 --> 00:42:59,720
And then you would have to set it up with a key vault.

644
00:42:59,720 --> 00:43:02,720
And then you would have to set it up with a key vault.

645
00:43:02,720 --> 00:43:05,720
And then you would have to set it up with a key vault.

646
00:43:05,720 --> 00:43:07,720
And then you would have to set it up with a key vault.

647
00:43:07,720 --> 00:43:09,720
And then you would have to set it up with a key vault.

648
00:43:09,720 --> 00:43:11,720
And then you would have to set it up with a key vault.

649
00:43:11,720 --> 00:43:14,720
And then you would have to set it up with a key vault.

650
00:43:14,720 --> 00:43:17,720
And then you would have to set it up with a key vault.

651
00:43:17,720 --> 00:43:20,720
And then you would have to set it up with a key vault.

652
00:43:20,720 --> 00:43:22,720
And then you would have to set it up with a key vault.

653
00:43:22,720 --> 00:43:23,720
And then you would have to set it up with a key vault.

654
00:43:23,720 --> 00:43:25,720
And then you would have to set it up with a key vault.

655
00:43:25,720 --> 00:43:26,720
And then you would have to set it up with a key vault.

656
00:43:26,720 --> 00:43:28,720
And then you would have to set it up with a key vault.

657
00:43:28,720 --> 00:43:29,720
And then you would have to set it up with a key vault.

658
00:43:29,720 --> 00:43:30,720
And then you would have to set it up with a key vault.

659
00:43:30,720 --> 00:43:31,720
And then you would have to set it up with a key vault.

660
00:43:31,720 --> 00:43:32,720
And then you would have to set it up with a key vault.

661
00:43:32,720 --> 00:43:33,720
And then you would have to set it up with a key vault.

662
00:43:33,720 --> 00:43:48,720
And then you would have to set it up with a key vault.

663
00:43:48,720 --> 00:43:51,720
And then you would have to set it up with a key vault.

664
00:43:51,720 --> 00:43:52,720
And then you would have to set it up with a key vault.

665
00:43:52,720 --> 00:43:54,720
And then you would have to set it up with a key vault.

666
00:43:54,720 --> 00:43:56,720
And then you would have to set it up with a key vault.

667
00:43:56,720 --> 00:43:57,720
And then you would have to set it up with a key vault.

668
00:43:57,720 --> 00:43:58,720
And then you would have to set it up with a key vault.

669
00:43:58,720 --> 00:43:59,720
And then you would have to set it up with a key vault.

670
00:43:59,720 --> 00:44:00,720
And then you would have to set it up with a key vault.

671
00:44:00,720 --> 00:44:01,720
And then you would have to set it up with a key vault.

672
00:44:01,720 --> 00:44:02,720
And then you would have to set it up with a key vault.

673
00:44:02,720 --> 00:44:04,720
And then you would have to set it up with a key vault.

674
00:44:04,720 --> 00:44:05,720
And then you would have to set it up with a key vault.

675
00:44:05,720 --> 00:44:06,720
And then you would have to set it up with a key vault.

676
00:44:06,720 --> 00:44:08,720
And then you would have to set it up with a key vault.

677
00:44:08,720 --> 00:44:09,720
And then you would have to set it up with a key vault.

678
00:44:09,720 --> 00:44:10,720
And then you would have to set it up with a key vault.

679
00:44:10,720 --> 00:44:11,720
And then you would have to set it up with a key vault.

680
00:44:11,720 --> 00:44:12,720
And then you would have to set it up with a key vault.

681
00:44:12,720 --> 00:44:13,720
And then you would have to set it up with a key vault.

682
00:44:13,720 --> 00:44:14,720
And then you would have to set it up with a key vault.

683
00:44:14,720 --> 00:44:15,720
And then you would have to set it up with a key vault.

684
00:44:15,720 --> 00:44:16,720
And then you would have to set it up with a key vault.

685
00:44:16,720 --> 00:44:17,720
And then you would have to set it up with a key vault.

686
00:44:17,720 --> 00:44:32,720
And then you would have to set it up with a key vault.

687
00:44:32,720 --> 00:44:35,720
And then you would have to set it up with a key vault.

688
00:44:35,720 --> 00:44:36,720
And then you would have to set it up with a key vault.

689
00:44:36,720 --> 00:44:38,720
And then you would have to set it up with a key vault.

690
00:44:38,720 --> 00:44:40,720
And then you would have to set it up with a key vault.

691
00:44:40,720 --> 00:44:41,720
And then you would have to set it up with a key vault.

692
00:44:41,720 --> 00:44:42,720
And then you would have to set it up with a key vault.

693
00:44:42,720 --> 00:44:43,720
And then you would have to set it up with a key vault.

694
00:44:43,720 --> 00:44:44,720
And then you would have to set it up with a key vault.

695
00:44:44,720 --> 00:44:45,720
And then you would have to set it up with a key vault.

696
00:44:45,720 --> 00:44:46,720
And then you would have to set it up with a key vault.

697
00:44:46,720 --> 00:44:48,720
And then you would have to set it up with a key vault.

698
00:44:48,720 --> 00:44:49,720
And then you would have to set it up with a key vault.

699
00:44:49,720 --> 00:44:50,720
And then you would have to set it up with a key vault.

700
00:44:50,720 --> 00:44:52,720
And then you would have to set it up with a key vault.

701
00:44:52,720 --> 00:44:53,720
And then you would have to set it up with a key vault.

702
00:44:53,720 --> 00:44:55,720
And then you would have to set it up with a key vault.

703
00:44:55,720 --> 00:44:56,720
And then you would have to set it up with a key vault.

704
00:44:56,720 --> 00:44:57,720
And then you would have to set it up with a key vault.

705
00:44:57,720 --> 00:44:58,720
And then you would have to set it up with a key vault.

706
00:44:58,720 --> 00:44:59,720
And then you would have to set it up with a key vault.

707
00:44:59,720 --> 00:45:00,720
And then you would have to set it up with a key vault.

708
00:45:00,720 --> 00:45:01,720
And then you would have to set it up with a key vault.

709
00:45:01,720 --> 00:45:02,720
And then you would have to set it up with a key vault.

710
00:45:02,720 --> 00:45:17,720
And then you would have to set it up with a key vault.

711
00:45:17,720 --> 00:45:20,720
And then you would have to set it up with a key vault.

712
00:45:20,720 --> 00:45:21,720
And then you would have to set it up with a key vault.

713
00:45:21,720 --> 00:45:23,720
And then you would have to set it up with a key vault.

714
00:45:23,720 --> 00:45:25,720
And then you would have to set it up with a key vault.

715
00:45:25,720 --> 00:45:26,720
And then you would have to set it up with a key vault.

716
00:45:26,720 --> 00:45:27,720
And then you would have to set it up with a key vault.

717
00:45:27,720 --> 00:45:28,720
And then you would have to set it up with a key vault.

718
00:45:28,720 --> 00:45:29,720
And then you would have to set it up with a key vault.

719
00:45:29,720 --> 00:45:30,720
And then you would have to set it up with a key vault.

720
00:45:30,720 --> 00:45:31,720
And then you would have to set it up with a key vault.

721
00:45:31,720 --> 00:45:33,720
And then you would have to set it up with a key vault.

722
00:45:33,720 --> 00:45:34,720
And then you would have to set it up with a key vault.

723
00:45:34,720 --> 00:45:35,720
And then you would have to set it up with a key vault.

724
00:45:35,720 --> 00:45:37,720
And then you would have to set it up with a key vault.

725
00:45:37,720 --> 00:45:38,720
And then you would have to set it up with a key vault.

726
00:45:38,720 --> 00:45:39,720
And then you would have to set it up with a key vault.

727
00:45:39,720 --> 00:45:40,720
And then you would have to set it up with a key vault.

728
00:45:40,720 --> 00:45:41,720
And then you would have to set it up with a key vault.

729
00:45:41,720 --> 00:45:42,720
And then you would have to set it up with a key vault.

730
00:45:42,720 --> 00:45:43,720
And then you would have to set it up with a key vault.

731
00:45:43,720 --> 00:45:44,720
And then you would have to set it up with a key vault.

732
00:45:44,720 --> 00:45:45,720
And then you would have to set it up with a key vault.

733
00:45:45,720 --> 00:45:46,720
And then you would have to set it up with a key vault.

734
00:45:46,720 --> 00:46:01,720
And then you would have to set it up with a key vault.

735
00:46:01,720 --> 00:46:04,720
And then you would have to set it up with a key vault.

736
00:46:04,720 --> 00:46:05,720
And then you would have to set it up with a key vault.

737
00:46:05,720 --> 00:46:07,720
And then you would have to set it up with a key vault.

738
00:46:07,720 --> 00:46:09,720
And then you would have to set it up with a key vault.

739
00:46:09,720 --> 00:46:11,720
And then you would have to set it up with a key vault.

740
00:46:11,720 --> 00:46:13,720
And then you would have to set it up with a key vault.

741
00:46:13,720 --> 00:46:14,720
And then you would have to set it up with a key vault.

742
00:46:14,720 --> 00:46:16,720
And then you would have to set it up with a key vault.

743
00:46:16,720 --> 00:46:18,720
And then you would have to set it up with a key vault.

744
00:46:18,720 --> 00:46:20,720
And then you would have to set it up with a key vault.

745
00:46:20,720 --> 00:46:21,720
And then you would have to set it up with a key vault.

746
00:46:21,720 --> 00:46:23,720
And then you would have to set it up with a key vault.

747
00:46:23,720 --> 00:46:24,720
And then you would have to set it up with a key vault.

748
00:46:24,720 --> 00:46:25,720
And then you would have to set it up with a key vault.

749
00:46:25,720 --> 00:46:26,720
And then you would have to set it up with a key vault.

750
00:46:26,720 --> 00:46:27,720
And then you would have to set it up with a key vault.

751
00:46:27,720 --> 00:46:28,720
And then you would have to set it up with a key vault.

752
00:46:28,720 --> 00:46:29,720
And then you would have to set it up with a key vault.

753
00:46:29,720 --> 00:46:30,720
And then you would have to set it up with a key vault.

754
00:46:30,720 --> 00:46:31,720
And then you would have to set it up with a key vault.

755
00:46:31,720 --> 00:46:46,720
And then you would have to set it up with a key vault.

756
00:46:46,720 --> 00:46:48,720
And then you would have to set it up with a key vault.

757
00:46:48,720 --> 00:46:50,720
And then you would have to set it up with a key vault.

758
00:46:50,720 --> 00:46:52,720
And then you would have to set it up with a key vault.

759
00:46:52,720 --> 00:46:54,720
And then you would have to set it up with a key vault.

760
00:46:54,720 --> 00:46:55,720
And then you would have to set it up with a key vault.

761
00:46:55,720 --> 00:46:56,720
And then you would have to set it up with a key vault.

762
00:46:56,720 --> 00:46:57,720
And then you would have to set it up with a key vault.

763
00:46:57,720 --> 00:46:58,720
And then you would have to set it up with a key vault.

764
00:46:58,720 --> 00:46:59,720
And then you would have to set it up with a key vault.

765
00:46:59,720 --> 00:47:00,720
And then you would have to set it up with a key vault.

766
00:47:00,720 --> 00:47:02,720
And then you would have to set it up with a key vault.

767
00:47:02,720 --> 00:47:03,720
And then you would have to set it up with a key vault.

768
00:47:03,720 --> 00:47:04,720
And then you would have to set it up with a key vault.

769
00:47:04,720 --> 00:47:06,720
And then you would have to set it up with a key vault.

770
00:47:06,720 --> 00:47:07,720
And then you would have to set it up with a key vault.

771
00:47:07,720 --> 00:47:09,720
And then you would have to set it up with a key vault.

772
00:47:09,720 --> 00:47:10,720
And then you would have to set it up with a key vault.

773
00:47:10,720 --> 00:47:11,720
And then you would have to set it up with a key vault.

774
00:47:11,720 --> 00:47:12,720
And then you would have to set it up with a key vault.

775
00:47:12,720 --> 00:47:13,720
And then you would have to set it up with a key vault.

776
00:47:13,720 --> 00:47:14,720
And then you would have to set it up with a key vault.

777
00:47:14,720 --> 00:47:15,720
And then you would have to set it up with a key vault.

778
00:47:15,720 --> 00:47:16,720
And then you would have to set it up with a key vault.

779
00:47:16,720 --> 00:47:31,720
And then you would have to set it up with a key vault.

780
00:47:31,720 --> 00:47:34,720
And then you would have to set it up with a key vault.

781
00:47:34,720 --> 00:47:35,720
And then you would have to set it up with a key vault.

782
00:47:35,720 --> 00:47:37,720
And then you would have to set it up with a key vault.

783
00:47:37,720 --> 00:47:38,720
And then you would have to set it up with a key vault.

784
00:47:38,720 --> 00:47:39,720
And then you would have to set it up with a key vault.

785
00:47:39,720 --> 00:47:40,720
And then you would have to set it up with a key vault.

786
00:47:40,720 --> 00:47:41,720
And then you would have to set it up with a key vault.

787
00:47:41,720 --> 00:47:42,720
And then you would have to set it up with a key vault.

788
00:47:42,720 --> 00:47:43,720
And then you would have to set it up with a key vault.

789
00:47:43,720 --> 00:47:44,720
And then you would have to set it up with a key vault.

790
00:47:44,720 --> 00:47:45,720
And then you would have to set it up with a key vault.

791
00:47:45,720 --> 00:47:47,720
And then you would have to set it up with a key vault.

792
00:47:47,720 --> 00:47:48,720
And then you would have to set it up with a key vault.

793
00:47:48,720 --> 00:47:49,720
And then you would have to set it up with a key vault.

794
00:47:49,720 --> 00:47:51,720
And then you would have to set it up with a key vault.

795
00:47:51,720 --> 00:47:52,720
And then you would have to set it up with a key vault.

796
00:47:52,720 --> 00:47:53,720
And then you would have to set it up with a key vault.

797
00:47:53,720 --> 00:47:54,720
And then you would have to set it up with a key vault.

798
00:47:54,720 --> 00:47:55,720
And then you would have to set it up with a key vault.

799
00:47:55,720 --> 00:47:56,720
And then you would have to set it up with a key vault.

800
00:47:56,720 --> 00:47:57,720
And then you would have to set it up with a key vault.

801
00:47:57,720 --> 00:47:58,720
And then you would have to set it up with a key vault.

802
00:47:58,720 --> 00:47:59,720
And then you would have to set it up with a key vault.

803
00:47:59,720 --> 00:48:00,720
And then you would have to set it up with a key vault.

804
00:48:00,720 --> 00:48:15,720
And then you would have to set it up with a key vault.

805
00:48:15,720 --> 00:48:18,720
And then you would have to set it up with a key vault.

806
00:48:18,720 --> 00:48:19,720
And then you would have to set it up with a key vault.

807
00:48:19,720 --> 00:48:20,720
And then you would have to set it up with a key vault.

808
00:48:20,720 --> 00:48:21,720
And then you would have to set it up with a key vault.

809
00:48:21,720 --> 00:48:22,720
And then you would have to set it up with a key vault.

810
00:48:22,720 --> 00:48:23,720
And then you would have to set it up with a key vault.

811
00:48:23,720 --> 00:48:24,720
And then you would have to set it up with a key vault.

812
00:48:24,720 --> 00:48:25,720
And then you would have to set it up with a key vault.

813
00:48:25,720 --> 00:48:26,720
And then you would have to set it up with a key vault.

814
00:48:26,720 --> 00:48:27,720
And then you would have to set it up with a key vault.

815
00:48:27,720 --> 00:48:28,720
And then you would have to set it up with a key vault.

816
00:48:28,720 --> 00:48:29,720
And then you would have to set it up with a key vault.

817
00:48:29,720 --> 00:48:31,720
And then you would have to set it up with a key vault.

818
00:48:31,720 --> 00:48:39,720
And then you would have to set it up with a key vault.

819
00:48:39,720 --> 00:48:48,720
And then you would have to set it up with a key vault.

820
00:48:48,720 --> 00:48:51,720
And then you would have to set it up with a key vault.

821
00:48:51,720 --> 00:48:52,720
And then you would have to set it up with a key vault.

822
00:48:52,720 --> 00:48:53,720
And then you would have to set it up with a key vault.

823
00:48:53,720 --> 00:48:54,720
And then you would have to set it up with a key vault.

824
00:48:54,720 --> 00:48:55,720
And then you would have to set it up with a key vault.

825
00:48:55,720 --> 00:48:56,720
And then you would have to set it up with a key vault.

826
00:48:56,720 --> 00:48:57,720
And then you would have to set it up with a key vault.

827
00:48:57,720 --> 00:48:58,720
And then you would have to set it up with a key vault.

828
00:48:58,720 --> 00:49:00,720
And then you would have to set it up with a key vault.

829
00:49:00,720 --> 00:49:02,720
And then you would have to set it up with a key vault.

830
00:49:02,720 --> 00:49:04,720
And then you would have to set it up with a key vault.

831
00:49:04,720 --> 00:49:05,720
And then you would have to set it up with a key vault.

832
00:49:05,720 --> 00:49:07,720
And then you would have to set it up with a key vault.

833
00:49:07,720 --> 00:49:08,720
And then you would have to set it up with a key vault.

834
00:49:08,720 --> 00:49:09,720
And then you would have to set it up with a key vault.

835
00:49:09,720 --> 00:49:10,720
And then you would have to set it up with a key vault.

836
00:49:10,720 --> 00:49:11,720
And then you would have to set it up with a key vault.

837
00:49:11,720 --> 00:49:12,720
And then you would have to set it up with a key vault.

838
00:49:12,720 --> 00:49:13,720
And then you would have to set it up with a key vault.

839
00:49:13,720 --> 00:49:14,720
And then you would have to set it up with a key vault.

840
00:49:14,720 --> 00:49:15,720
And then you would have to set it up with a key vault.

841
00:49:15,720 --> 00:49:30,720
And then you would have to set it up with a key vault.

842
00:49:30,720 --> 00:49:40,720
And then you would have to set it up with a key vault.

843
00:49:40,720 --> 00:49:50,720
And then you would have to set it up with a key vault.

844
00:49:50,720 --> 00:49:52,720
And then you would have to set it up with a key vault.

845
00:49:52,720 --> 00:49:54,720
And then you would have to set it up with a key vault.

846
00:49:54,720 --> 00:49:58,720
And then you would have to set it up with a key vault.

847
00:49:58,720 --> 00:49:59,720
And then you would have to set it up with a key vault.

848
00:49:59,720 --> 00:50:00,720
And then you would have to set it up with a key vault.

849
00:50:00,720 --> 00:50:01,720
And then you would have to set it up with a key vault.

850
00:50:01,720 --> 00:50:02,720
And then you would have to set it up with a key vault.

851
00:50:02,720 --> 00:50:03,720
And then you would have to set it up with a key vault.

852
00:50:03,720 --> 00:50:04,720
And then you would have to set it up with a key vault.

853
00:50:04,720 --> 00:50:05,720
And then you would have to set it up with a key vault.

854
00:50:05,720 --> 00:50:06,720
And then you would have to set it up with a key vault.

855
00:50:06,720 --> 00:50:07,720
And then you would have to set it up with a key vault.

856
00:50:07,720 --> 00:50:17,720
And then you would have to set it up with a key vault.

857
00:50:17,720 --> 00:50:19,720
And then you would have to set it up with a key vault.

858
00:50:19,720 --> 00:50:21,720
And then you would have to set it up with a key vault.

859
00:50:21,720 --> 00:50:22,720
And then you would have to set it up with a key vault.

860
00:50:22,720 --> 00:50:24,720
And then you would have to set it up with a key vault.

861
00:50:24,720 --> 00:50:25,720
And then you would have to set it up with a key vault.

862
00:50:25,720 --> 00:50:26,720
And then you would have to set it up with a key vault.

863
00:50:26,720 --> 00:50:27,720
And then you would have to set it up with a key vault.

864
00:50:27,720 --> 00:50:28,720
And then you would have to set it up with a key vault.

865
00:50:28,720 --> 00:50:29,720
And then you would have to set it up with a key vault.

866
00:50:29,720 --> 00:50:30,720
And then you would have to set it up with a key vault.

867
00:50:30,720 --> 00:50:31,720
And then you would have to set it up with a key vault.

868
00:50:31,720 --> 00:50:32,720
And then you would have to set it up with a key vault.

869
00:50:32,720 --> 00:50:42,720
And then you would have to set it up with a key vault.

870
00:50:42,720 --> 00:50:44,720
And then you would have to set it up with a key vault.

871
00:50:44,720 --> 00:50:46,720
And then you would have to set it up with a key vault.

872
00:50:46,720 --> 00:50:47,720
And then you would have to set it up with a key vault.

873
00:50:47,720 --> 00:50:50,720
And then you would have to set it up with a key vault.

874
00:50:50,720 --> 00:50:51,720
And then you would have to set it up with a key vault.

875
00:50:51,720 --> 00:50:52,720
And then you would have to set it up with a key vault.

876
00:50:52,720 --> 00:50:53,720
And then you would have to set it up with a key vault.

877
00:50:53,720 --> 00:50:54,720
And then you would have to set it up with a key vault.

878
00:50:54,720 --> 00:50:55,720
And then you would have to set it up with a key vault.

879
00:50:55,720 --> 00:50:56,720
And then you would have to set it up with a key vault.

880
00:50:56,720 --> 00:50:57,720
And then you would have to set it up with a key vault.

881
00:50:57,720 --> 00:50:58,720
And then you would have to set it up with a key vault.

882
00:50:58,720 --> 00:51:08,720
And then you would have to set it up with a key vault.

883
00:51:08,720 --> 00:51:10,720
And then you would have to set it up with a key vault.

884
00:51:10,720 --> 00:51:12,720
And then you would have to set it up with a key vault.

885
00:51:12,720 --> 00:51:13,720
And then you would have to set it up with a key vault.

886
00:51:13,720 --> 00:51:16,720
And then you would have to set it up with a key vault.

887
00:51:16,720 --> 00:51:17,720
And then you would have to set it up with a key vault.

888
00:51:17,720 --> 00:51:18,720
And then you would have to set it up with a key vault.

889
00:51:18,720 --> 00:51:19,720
And then you would have to set it up with a key vault.

890
00:51:19,720 --> 00:51:20,720
And then you would have to set it up with a key vault.

891
00:51:20,720 --> 00:51:21,720
And then you would have to set it up with a key vault.

892
00:51:21,720 --> 00:51:22,720
And then you would have to set it up with a key vault.

893
00:51:22,720 --> 00:51:23,720
And then you would have to set it up with a key vault.

894
00:51:23,720 --> 00:51:24,720
And then you would have to set it up with a key vault.

895
00:51:24,720 --> 00:51:34,720
And then you would have to set it up with a key vault.

896
00:51:34,720 --> 00:51:36,720
And then you would have to set it up with a key vault.

897
00:51:36,720 --> 00:51:38,720
And then you would have to set it up with a key vault.

898
00:51:38,720 --> 00:51:39,720
And then you would have to set it up with a key vault.

899
00:51:39,720 --> 00:51:41,720
And then you would have to set it up with a key vault.

900
00:51:41,720 --> 00:51:42,720
And then you would have to set it up with a key vault.

901
00:51:42,720 --> 00:51:43,720
And then you would have to set it up with a key vault.

902
00:51:43,720 --> 00:51:44,720
And then you would have to set it up with a key vault.

903
00:51:44,720 --> 00:51:45,720
And then you would have to set it up with a key vault.

904
00:51:45,720 --> 00:51:46,720
And then you would have to set it up with a key vault.

905
00:51:46,720 --> 00:51:47,720
And then you would have to set it up with a key vault.

906
00:51:47,720 --> 00:51:48,720
And then you would have to set it up with a key vault.

907
00:51:48,720 --> 00:51:49,720
And then you would have to set it up with a key vault.

908
00:51:49,720 --> 00:51:57,720
Yeah, we're working on that, on starting that edition up, also within a month, I think.

909
00:51:57,720 --> 00:52:03,720
So that's, that takes up a lot of my time.

910
00:52:03,720 --> 00:52:13,720
Yeah, so really great interview and, and yeah, so then my closing flight.

911
00:52:13,720 --> 00:52:19,720
And then there is what the thing, the most important piece of advice you give to organization, build modern.

912
00:52:19,720 --> 00:52:27,720
And then there is what the thing, the most important piece of advice you give to organization.

913
00:52:27,720 --> 00:52:28,720
Build modern.

914
00:52:28,720 --> 00:52:29,720
Build modern.

915
00:52:29,720 --> 00:52:29,720
And then you give to organization.

916
00:52:29,720 --> 00:52:30,720
Build modern.

917
00:52:30,720 --> 00:52:31,720
And then you give to organization.

918
00:52:31,720 --> 00:52:32,720
Build modern.

919
00:52:32,720 --> 00:52:34,720
And then you give to organization.

920
00:52:34,720 --> 00:52:35,720
Build modern.

921
00:52:35,720 --> 00:52:35,720
And then you give to organization.

922
00:52:35,720 --> 00:52:36,720
Build modern.

923
00:52:36,720 --> 00:52:37,720
And then you give to organization.

924
00:52:37,720 --> 00:52:38,720
Build modern.

925
00:52:38,720 --> 00:52:39,720
And then you give to organization.

926
00:52:39,720 --> 00:52:40,720
Build modern.

927
00:52:40,720 --> 00:52:41,720
Build modern.

928
00:52:41,720 --> 00:52:41,720
Build modern.

929
00:52:41,720 --> 00:52:42,720
And then you give to organization.

930
00:52:42,720 --> 00:52:50,220
To the middle of the night, and you have a P1 priority, a urgent problem.

931
00:52:50,220 --> 00:52:52,760
And you need to click something to get things working go ahead.

932
00:52:52,760 --> 00:52:56,800
But make sure you feed it back into code.

933
00:52:56,800 --> 00:53:00,460
Yeah, then, Rex, thank you so much for joining the show.

934
00:53:00,460 --> 00:53:04,820
It was a fantastic conversation, because we covered the foundation,

935
00:53:04,820 --> 00:53:09,140
that every successful cloud environment depends on networking.

936
00:53:09,140 --> 00:53:13,220
We explore Azure virtual, major infrastructure as a code,

937
00:53:13,220 --> 00:53:17,800
secure Azure functions, zero trust, hybrid connectivity,

938
00:53:17,800 --> 00:53:21,860
and by automation is no longer a general in modern cloud architecture.

939
00:53:21,860 --> 00:53:26,900
Yeah, one of the biggest takeaways is for me is, yeah,

940
00:53:26,900 --> 00:53:32,220
it's a great cloud architecture doesn't happen by accident.

941
00:53:32,220 --> 00:53:36,260
It starts with networking, fundamentals, consistent automation,

942
00:53:36,260 --> 00:53:40,500
and security built into every layer from the very beginning.

943
00:53:40,500 --> 00:53:44,420
Yeah, so thank you so much for staying with me here.

944
00:53:44,420 --> 00:53:49,060
And yeah, hope you've seen us again on the meeting, podcasts,

945
00:53:49,060 --> 00:53:50,860
livestream, and so on.

946
00:53:50,860 --> 00:53:52,100
Thank you so much.

947
00:53:52,100 --> 00:53:53,060
Yeah, thank you for having me.

948
00:53:53,060 --> 00:53:56,260
It was really a pleasure and a lot of the talk.

949
00:53:56,260 --> 00:53:58,540
So awesome, thank you very much.

950
00:53:58,540 --> 00:54:08,540
[BLANK_AUDIO]

Mirko Peters

Founder of m365.fm, m365.show and m365con.net

Mirko Peters is a Microsoft 365 expert, content creator, and founder of m365.fm, a platform dedicated to sharing practical insights on modern workplace technologies. His work focuses on Microsoft 365 governance, security, collaboration, and real-world implementation strategies.

Through his podcast and written content, Mirko provides hands-on guidance for IT professionals, architects, and business leaders navigating the complexities of Microsoft 365. He is known for translating complex topics into clear, actionable advice, often highlighting common mistakes and overlooked risks in real-world environments.

With a strong emphasis on community contribution and knowledge sharing, Mirko is actively building a platform that connects experts, shares experiences, and helps organizations get the most out of their Microsoft 365 investments.

Rex de Koning

Senior Cloud Engineer

Rex is in IT for about 30 years, having several functions. Started as a software devleoper, making the step to system -and network engineering and after that, after a brief detour via AWS landed in the Microsoft Cloud Ecosystem.

Rex is an MCT and MVP Azure Networking, focussing on Axure Cloud, Networking and IaC. He also is orginazer of some Community Events and loves to volunteer and speak at events.