Microsoft Whiteboard is a free desktop drawing whiteboard application, but incorporates many other features such as note-taking, drawing, sketching, and cloud storage. Whiteboard allows teams to collaborate in real-time, wherever you are, and make your ideas available to colleagues to grow together with an infinite canvas designed on stylus, digital artboards …
How can the whiteboard be turned on or off?
Whiteboard is automatically enabled for Office 365 users.
Windows 10, iOS and web users, users can download the app for their respective platforms and sign in, unless you have chosen to disable the service.
To turn Microsoft Whiteboard on or off, do the following:
How can whiteboard for the web be turned on or off?
Toggle Microsoft Whiteboard for your organization including across Windows, ios, and Web devices.
What compliance standards does Microsoft Whiteboard meet?
Whiteboard on Windows 10, Surface Hub, iOS and web tier C meetings, this means they conform to common standards including SOC 1, SOC 2, ISO 27001, HIPAA and EU and model clauses.
Whiteboard does not yet support eDiscovery, Hold Policy or Legal Retention. This feature plan will be developed in the future
More reference: Microsoft Whiteboard User Guide
Follow SUSE’s SP7 procedure to enable FIPS mode, reboot safely, verify the active policy, and check whether your compliance requirement calls for validated modules.
Compare YaST and cryptsetup for a new encrypted SLES data volume, choose LUKS1 or LUKS2, and verify unlock and mount behavior safely.
Create, refine, and verify a least-privilege AppArmor profile on SLES 15 SP7, with a clear note on SLES 16’s SELinux default.
Set up RMT on SLES 15, mirror entitled repositories, and verify HTTPS registration and package access from a test client.
Connect SLES 15 to AD with YaST’s SSSD-based logon management, then verify directory lookup, domain login, and Kerberos tickets.
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.
