Dual Boot with Windows 10 Pro Bitlocker

I have not done Dual Boot with Windows 10 Pro and Bitlocker before, so I have a few questions.

This suggest disabling Bitlocker before installing Linux.
Dual Booting Ubuntu With Windows 10 Pro With BitLocker Encryption - It’s FOSS (itsfoss.com)

This does not suggest disabling Bitlocker. Although it does say I might be prompted for the Bitlocker Recovery Key after installation.
Dual-booting Linux with BitLocker Device Encryption and Secure Boot | Ctrl blog
It suggest sharing the UEFI partition with Windows, not creating a new /boot/efi.

I am not sure I have access to disable Bitlocker on my PC.
Is it possible to install Linux on Dual Boot, if I do not have access to Bitlocker?

Would it be easier and less troublesome to install Linux on a separate disk?

There was a recent article on Phoronix with some problems with Bitlocker and Dual Boot.
Increased Use Of Windows BitLocker Is Causing Headaches For Linux Dual Booting - Phoronix

Some suggest using the EFI boot menu, and not Grub. Is that a good option to avoid problems with Bitlocker? I wonder if this is the option some calls systemd-boot. Is this an option during OpenSUSE installation procedure?

If Bitlocker is configured to use TPM you must have Administrator rights to obtain recovery key. If you do not have Administrator and do not have recovery key, you will lose your data.

If Bitlocker is configured to request password on startup, I do not see any problems for dual boot (except inability to resize Windows partition from within Linux).

It does not request a password during boot, so I guess then it is using TPM.

I was able to back up my Bitlocker recovery key in Windows “Manage Bitlocker”, with “Launch with elevated privileges” and “Save to you Azure AD account”.

If you have full access to Windows administration, you should be able to see exact Bitlocker configuration, in GUI or using manage-bde command, there is no need to guess.

You will need to have your recovery key before you and enter on startup to boot Windows, having it in AD does not help.

Anyway - when using TPM I would say that choosing OS via your BIOS boot menu is the safest method. Using standard chainloading from grub will prevent automatic unlock. Leap does not integrate systemd-boot yet.

Whether you use shared ESP or dedicate ESP to each operating system is irrelevant. Just be careful to not format shared ESP during installation. As one of your links recommends, make sure to have bootable Windows for recovery.

P.S. it sounds like it is your corporate system. Are you even allowed to do what you intend to do? Besides, on my previous work system I could not boot from USB (I am still curious how it was achieved).

Is this planned to be included in a future Leap release?

I don’t want to mess around with ESP, so I think I will wait until systemd-boot is integrated in Leap. In the meantime I think I will use Leap in a VM on Windows.

I am allowed to install Linux on my corporate laptop, but since Linux is not supported I don’t get support/help from our IT Department.

What do you mean “included”? Binary should be already available, but it is not integrated in installer/YaST/kernel updates etc. Only recently basic support in update-bootloader was added in Tumbleweed, which at least makes it possible to manually configure systemd-boot as default.

I am pretty sure nothing will change for Leap 15 and nobody knows what happens next.

I am not sure I understand it. You need to install Linux bootloader on ESP anyway, be it grub or systemd-boot.

What you mentioned.

Just be careful to not format shared ESP during installation.

Is it not enough to mount the existing ESP during installation setup?

Yes, of course, it is enough.