Microsoft OneDrive is one of the data sharing options. You can upload and share files on OneDrive just like on Google Drive. When we share many files via OneDrive, managing files is essential. Here is a guide to customize OneDrive link protection.
How to protect sharing links on OneDrive
Step 1:
On the OneDrive interface, find the file you want to share and click on the file sharing icon .
Step 2:
Displays the interface for customizing shared files on OneDrive. First, the user clicks on the pen icon and then selects the mode in which the object can act with this file.
Step 3:
Continue to click on customize receive OneDrive file sharing link to adjust who can access this sharing link.
Step 4:
In this new interface you choose who to share the activity link with , to everyone or only those you tag the account.
If you choose Anyone , below you will find additional settings for actions with shared files, set file sharing expiration dates , and set file sharing passwords on OneDrive.
Set up the right Live Patching path for SLES 16.0 or 15 SP7, apply eligible kernel fixes, and confirm what is active without confusing it with a reboot-required kernel update.
Load a custom SLES 15 kernel module without disabling Secure Boot. Match the running kernel, sign the .ko file, enroll a MOK key, and verify loading.
SLES 15 SP5 can migrate online to SP6, but each node must reboot. Use a tested rolling upgrade or blue-green cutover to keep workloads reachable.
Use SUSE’s supported STIG profile to scan SLES 15, test remediation, review remaining findings, and retain assessment evidence.
Trace a failed Cockpit connection through DNS, port 9090, the systemd socket, firewalld, TLS, and login settings using current SUSE guidance.
Create a redundant Ethernet connection on SLES 15 with YaST and Wicked, configure active-backup bonding, and verify both ports and failover.
Turn an existing SLES 15 system into a reviewed AutoYaST profile, validate it, and use it to deploy a test server with fewer manual steps.
Install the SLES 15 KVM and libvirt tools, enable the right host service, and configure selected virtual machines to start after a reboot.
Use systemd jobs and the previous boot journal to locate a slow service, mount, or storage dependency, then correct it without masking the cause.
Use firewall-cmd to inspect the active zone, allow HTTP safely, preserve SSH access, and verify that the rule survives a reload on SLES 15.
