Add Intune, OPNSense, pfSense Videos (#431)

src/pages/how-to/installation/opnsense.mdx

@@ -3,6 +3,11 @@
 The NetBird client (agent) allows a peer to join a pre-existing NetBird deployment. If a NetBird deployment is not yet available,
 there are both managed and [self-hosted](https://docs.netbird.io/selfhosted/selfhosted-quickstart) options available.
 
+
+<div className="videowrapper">
+    <iframe src="https://www.youtube.com/embed/AK0Ct-ULFKg?start=669" allow="fullscreen;"></iframe>
+</div>
+
 <Note>
     The NetBird package is officially included starting from OPNsense `25.7.3`.
 </Note>

src/pages/how-to/installation/pfsense.mdx

@@ -7,6 +7,9 @@ there are both managed and [self-hosted](https://docs.netbird.io/selfhosted/self
 This installation is intended for early adopters while the pfSense package is under review and not yet available in the pfSense package manager.
 </Note>
 
+<div className="videowrapper">
+    <iframe src="https://www.youtube.com/embed/Kgrcquyeohc" allow="fullscreen;"></iframe>
+</div>
 
 ## Prerequisites
 - Shell/SSH access to pfSense (via Web UI shell or remote SSH)

src/pages/how-to/intune-mdm.mdx

@@ -1,5 +1,9 @@
 # Allow Only Intune-Managed Devices to Access Your Network
 
+<div className="videowrapper">
+    <iframe src="https://www.youtube.com/embed/W4DaE4Dj04o" allow="fullscreen;"></iframe>
+</div>
+
 <Note>
     TLDR: Devices marked as "Non-compliant" in Intune will automatically lose access, ensuring strict adherence to your security policies.
     Once a device returns to a "Compliant" status, access is restored.