Copilot now also has a voice chat option in addition to manually entering questions. Users can ask any question and Copilot will respond to you immediately. Copilot recognizes voice and converts it to text quickly and accurately. The article below will guide you to chat by voice on Copilot.
How to voice chat on Copilot
Step 1:
At the interface on Copilot, click on the microphone icon to use. Then you need to agree to let Copilot use the microphone on the device.
Step 2:
Now you will click on the microphone icon below to activate voice chat mode on Copilot. We clearly and precisely state the request to Copilot. Immediately after that you will see the content of the question displayed in text form, click the send icon to send.
Step 3:
We wait for the response from Copilot as usual. The response from Copilot is still very detailed to the user.
Step 4:
To continue voice chatting on Copilot, just click on the blue microphone icon below.
Video tutorial for voice chat on Copilot
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.
