home.social

#microsoft-teams — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #microsoft-teams, aggregated by home.social.

fetched live
  1. Schwarze Fenster bei der Bildschirmfreigabe: #MicrosoftTeams plagt derzeit Mac-Nutzer. Abhilfe schaffen ein aktuelles Update oder eine clevere Einstellung in den Optionen. #macOS winfuture.de/news,159925.html?

  2. Schwarze Fenster bei der Bildschirmfreigabe: #MicrosoftTeams plagt derzeit Mac-Nutzer. Abhilfe schaffen ein aktuelles Update oder eine clevere Einstellung in den Optionen. #macOS winfuture.de/news,159925.html?

  3. What's New in Office 365, Tuesday, July 07, 2026
    8 new posts across 5 Microsoft websites since Friday, July 03, 2026

    #Microsoft365 #Office365 #MicrosoftTeams #Microsoft365Copilot #PowerBI

    • Copilot for Microsoft 365 (2)
    • Microsoft 365 Blog - Tech Community (1)
    • Microsoft 365 Insider Blog (2)

    ..and more: o365.cannell.org/2026/07/07/wh

  4. Microsoft Teams: Automatic Call Recording & Transcription

    In August 2026 Microsoft has planned to start the rollout to configure automatic call recording and transcription for Teams Call Queues. Don’t be afraid. It’s off by default as far as I read and a Teams Admin must enable it per Call Queue.

    The complete announcement can be read in the roadmap ID 565215 and in the message center notification MC1401299.

    Source: Microsoft 365 Roadmap ID 565215

    Configuration, enabling it, is no technical complicated task but compliance and regulation must be clarified to ensure it is implemented the correctly, aligned with regulations and compliance. It should be enabled only on Teams Call Queues which the feature required and not solved by another (third-party) solution.

    Resources

    #Calling #MicrosoftTeams #Telephony
  5. Unlock Efficiency with Teams Phone Agent for AI-Powered Calls

    In the Teams Phone space there was another interesting announcement recently which caught my attention: Teams Phone Agent. It is available for organizations participating in the Frontier program. I.e. Frontier companies are organizations leveraging the latest innovation in AI with early feature access to advance business outcomes earlier.

    The Teams Phone Agent could add some more benefits and value to your organization’s telephony. You could make it work for you 24×7 and reduce the requirement that a person needs to answer each and every call because an agent could do this. Let me summarize and point out some highlights of the Teams Phone Agent.

    What is the Teams Phone Agent?

    The Teams Phone Agent is a new AI-powered capability that should help organizations to handle phone calls more efficiently especially during peak times. Combined with custom voice agents built in Microsoft Copilot Studio, businesses could automate specific phone calls and use cases, reduce wait times, and deliver faster resolutions. E.g. appointment scheduling, Q&A support, intelligent routing and transferring the caller to the appropriate, available callee, multi-lingual support. This can be accomplished by the Teams Phone Agent with its specific skills.

    For more specialized use cases you can build custom voice agents in Copilot Studio. E.g. for to check order status, billing inqueries.

    A Teams Phone Agent can get a Teams phone number and can get called directly.

    What are the requirements for Teams Phone Agent?

    Let me summarize the key requirements to get started with the Teams Phone Agent. Please note that these can be subject to change at any time and are just provided as-is.

    • Microsoft Teams Phone (System) incl. PSTN connectivity, licenses etc.
    • Participation in the Microsoft Frontier program (early access)
    • No additional licenses during public preview/frontier early access (as far as I read and understood?)
    • Teams Admin Center access to configure it
    • Copilot Studio for building and managing custom voice agents, knowledge bases, and orchestration logic…
    • Copilot Studio licenses for administration/configuration/…
    • Copilot Studio billing, e.g. consumption-based billing

    Other considerations to keep in mind before using Teams Phone Agent?

    Please note, using AI, an AI-agent might require a legal and compliance check before any implementation, especially in Germany. Regulations like GDPR, German Telecommunications Act (TKG) and others might be relevant and influence planning, configuration, implementation and operation. A Organization and IT staff remains responsible for how the AI is configured, what data it processes, and how callers are informed etc. Please involve and consult your legal advisor, data protection office, worker’s council, … and so on. This is a tip, a note but no legal advice at all.

    Conclusion, opinion and summary

    I like to utilize what I’ve got, so in case Teams calling is already in use, no third-party solution covering call flows and call interactions it might make sense to evaluate Teams Phone Agent, dive in a bit deeper to find out if your use cases for phone and calling scenarios benefit. In my experience companies are rarely having enough 24×7 people at the right time available for answering calls across different departments? That’s why the Teams Phone Agent could help with easy as well as more advanced requests coming in by phone call. Especially if you have something already available and running on Copilot Studio you might extend the use to callers as well?

    Resources

    #AIAgents #Calling #MicrosoftTeams #Telephony
  6. Microsoft Teams Built-in Agent Governance

    In the era of AI, agentic AI, developments and changes are released at a rapid pace. Staying on top of things is a challenge especially governing agents here and there. For Microsoft Teams a new capability to centrally govern built-in agents was recently announced as you can read in the Microsoft 365 message center notification MC1387573. It says that Teams admins get controls for Teams built-in agents to manage these by utilizing policies, user or group access assignments while also having more visibility for compliance purposes.

    Source: Microsoft 365 Roadmap ID 564766

    Currently the change is not available. At least not in lab tenant. The roadmap as well as the message center notification says that the rollout is scheduled to start in July 2026.

    You will notice this in your tenant, your Teams Admin Center, as soon as you get a new menu on the left blade Teams admin center > Teams apps > Built-in Teams agents. Based on the message center notification it look very similar to the Teams app management.

    Before and after the capability arrives in your Microsoft 365 tenant and Teams Admin Center there are few things you should do, three of them which are rather important are:

    • review your current org-wide app settings for Microsoft apps
      current org-wide app settings are no longer applied to built-in Teams agents
    • review and update agent-level permissions and configurations with the new controls
    • review settings and persons for this change

    Conclusion, opinion and summary

    In my opinion this can be a beneficial capability if you, as a Teams Admin, are required to configure more granular access and policies for built-in Teams agents. A common use case could be that you might want to introduce, allow and deploy built-in agents on your terms, step-by-step or in phases in conjunction with a suited change and adoption plan to ensure users know how to use these agents.

    However, I guess that many companies with the licenses might already have all of built-in agents enabled, not disabled? Now switching the approach, disabling built-in agents and planning to deploy these later on should be done with proper preparation and cautiously because turning it off might cause users being frustrated and irritated. Users might wonder: Why is something is gone out of a sudden, why was it taken away and now I have to ask for it? Better keep that in mind before implementing controls and governance after built-in agents might be widely in use.

    Resources

    #AI #AIAgents #Governance #MicrosoftTeams #TeamsAdminCenter
  7. Microsoft Teams Built-in Agent Governance

    In the era of AI, agentic AI, developments and changes are released at a rapid pace. Staying on top of things is a challenge especially governing agents here and there. For Microsoft Teams a new capability to centrally govern built-in agents was recently announced as you can read in the Microsoft 365 message center notification MC1387573. It says that Teams admins get controls for Teams built-in agents to manage these by utilizing policies, user or group access assignments while also having more visibility for compliance purposes.

    Source: Microsoft 365 Roadmap ID 564766

    Currently the change is not available. At least not in lab tenant. The roadmap as well as the message center notification says that the rollout is scheduled to start in July 2026.

    You will notice this in your tenant, your Teams Admin Center, as soon as you get a new menu on the left blade Teams admin center > Teams apps > Built-in Teams agents. Based on the message center notification it look very similar to the Teams app management.

    Before and after the capability arrives in your Microsoft 365 tenant and Teams Admin Center there are few things you should do, three of them which are rather important are:

    • review your current org-wide app settings for Microsoft apps
      current org-wide app settings are no longer applied to built-in Teams agents
    • review and update agent-level permissions and configurations with the new controls
    • review settings and persons for this change

    Conclusion, opinion and summary

    In my opinion this can be a beneficial capability if you, as a Teams Admin, are required to configure more granular access and policies for built-in Teams agents. A common use case could be that you might want to introduce, allow and deploy built-in agents on your terms, step-by-step or in phases in conjunction with a suited change and adoption plan to ensure users know how to use these agents.

    However, I guess that many companies with the licenses might already have all of built-in agents enabled, not disabled? Now switching the approach, disabling built-in agents and planning to deploy these later on should be done with proper preparation and cautiously because turning it off might cause users being frustrated and irritated. Users might wonder: Why is something is gone out of a sudden, why was it taken away and now I have to ask for it? Better keep that in mind before implementing controls and governance after built-in agents might be widely in use.

    Resources

    #AI #AIAgents #Governance #MicrosoftTeams #TeamsAdminCenter
  8. For those looking to manage their digital footprint on Microsoft Teams: learn how to effectively delete your activity data, including chat history and call logs. A clean slate can boost productivity and privacy.

    #MicrosoftTeams #Privacy #Tech #Productivity geekrewind.com/how-to-delete-y

  9. For those looking to manage their digital footprint on Microsoft Teams: learn how to effectively delete your activity data, including chat history and call logs. A clean slate can boost productivity and privacy.

    #MicrosoftTeams #Privacy #Tech #Productivity geekrewind.com/how-to-delete-y

  10. What's New in Office 365, Friday, July 03, 2026
    30 new posts across 13 Microsoft websites since Tuesday, June 30, 2026

    #Microsoft365 #Office365 #MicrosoftTeams #MicrosoftAzure #SharePoint #Microsoft365Copilot #PowerBI

    • SharePoint Blog (2)
    • Microsoft Azure Blog (6)
    • Microsoft 365 Developer Blog (2)

    ..and more: o365.cannell.org/2026/07/03/wh

  11. Microsoft has built a bouncer for Teams meetings. There is now a literal velvet rope for bots. 'Suspected threats' is an actual lobby category. We are so back to nightclub access control as enterprise IT policy

    #MicrosoftTeams #AIBots #EnterpriseIT #DigitalSovereignty #InfoSec #DataPrivacy #M365 #BotDetection #TechHumour #SovereignAuditor

  12. What's New in Office 365, Tuesday, June 30, 2026
    13 new posts across 12 Microsoft websites since Friday, June 26, 2026

    #Microsoft365 #Office365 #MicrosoftTeams #Microsoft365Copilot #MicrosoftAzure

    • Intune Customer Success (1)
    • Microsoft Azure Blog (1)
    • Microsoft 365 Developer Blog (1)

    ..and more: o365.cannell.org/2026/06/30/wh

  13. Hey IT guy/gal... here's a good update on what's been released this month!

    ▶️ What’s New in Microsoft 365 | June Updates
    youtube.com/watch?v=F8pondcaFo
    #Microsoft #Microsoft365 #Copilot #MicrosoftTeams

  14. Hey IT guy/gal... here's a good update on what's been released this month!

    ▶️ What’s New in Microsoft 365 | June Updates
    youtube.com/watch?v=F8pondcaFo
    #Microsoft #Microsoft365 #Copilot #MicrosoftTeams

  15. What's New in Office 365, Friday, June 26, 2026
    27 new posts across 14 Microsoft websites since Tuesday, June 23, 2026

    #Microsoft365 #Office365 #MicrosoftTeams #MicrosoftAzure #SharePoint #PowerBI

    • Azure AI Foundry Blog (4)
    • Viva Engage Blog (1)
    • Microsoft 365 Insider Blog (3)

    ..and more: o365.cannell.org/2026/06/26/wh

  16. Introducing the Keeper Teams App, an approval workflow that enables users to initiate and approve privileged access actions directly within Microsoft Teams. Users can manage:

    - Record and folder access requests
    - One-time share requests
    - Keeper Endpoint Privilege Manager approvals
    - SSO cloud device approvals
    - Create new login records

    The Keeper Teams App is powered by Keeper Secrets Manager and Commander Service Mode, preserving Keeper’s zero-knowledge security.

    #KeeperSecurity #MicrosoftTeams #Cybersecurity

  17. Introducing the Keeper Teams App, an approval workflow that enables users to initiate and approve privileged access actions directly within Microsoft Teams. Users can manage:

    - Record and folder access requests
    - One-time share requests
    - Keeper Endpoint Privilege Manager approvals
    - SSO cloud device approvals
    - Create new login records

    The Keeper Teams App is powered by Keeper Secrets Manager and Commander Service Mode, preserving Keeper’s zero-knowledge security.

    #KeeperSecurity #MicrosoftTeams #Cybersecurity

  18. Payouts King Ransomware Initial Access Broker Deploys New Edgecution Malware

    An initial access broker linked to Payouts King ransomware is deploying Edgecution, a sophisticated malware utilizing a malicious Microsoft Edge browser extension. The attack begins through social engineering via Microsoft Teams, impersonating IT staff and directing victims to fake Microsoft websites offering supposed Outlook updates. Edgecution comprises two components: a browser extension that communicates with command-and-control servers via websockets, and a Python-based backdoor. The extension abuses Chrome native messaging protocol to escape browser sandbox restrictions, enabling direct host access. This allows attackers to manipulate the filesystem, launch processes, and execute arbitrary code. The malware operates in a headless browser, remaining invisible to users. Deployment methods include AutoHotKey scripts, Windows batch scripts, and PowerShell scripts. The Python backdoor supports various commands including system information collection, filesystem access, and arbitrary code execution.

    Pulse ID: 6a3ab74e2728d85de0799971
    Pulse Link: otx.alienvault.com/pulse/6a3ab
    Pulse Author: AlienVault
    Created: 2026-06-23 16:41:50

    Be advised, this data is unverified and should be considered preliminary. Always do further verification.

    #BackDoor #Browser #Chrome #CyberSecurity #Edge #InfoSec #Malware #Microsoft #MicrosoftEdge #MicrosoftTeams #OTX #OpenThreatExchange #Outlook #PowerShell #Python #RAT #RansomWare #SocialEngineering #Windows #bot #AlienVault

  19. Payouts King Ransomware Initial Access Broker Deploys New Edgecution Malware

    An initial access broker linked to Payouts King ransomware is deploying Edgecution, a sophisticated malware utilizing a malicious Microsoft Edge browser extension. The attack begins through social engineering via Microsoft Teams, impersonating IT staff and directing victims to fake Microsoft websites offering supposed Outlook updates. Edgecution comprises two components: a browser extension that communicates with command-and-control servers via websockets, and a Python-based backdoor. The extension abuses Chrome native messaging protocol to escape browser sandbox restrictions, enabling direct host access. This allows attackers to manipulate the filesystem, launch processes, and execute arbitrary code. The malware operates in a headless browser, remaining invisible to users. Deployment methods include AutoHotKey scripts, Windows batch scripts, and PowerShell scripts. The Python backdoor supports various commands including system information collection, filesystem access, and arbitrary code execution.

    Pulse ID: 6a3ab74e2728d85de0799971
    Pulse Link: otx.alienvault.com/pulse/6a3ab
    Pulse Author: AlienVault
    Created: 2026-06-23 16:41:50

    Be advised, this data is unverified and should be considered preliminary. Always do further verification.

    #BackDoor #Browser #Chrome #CyberSecurity #Edge #InfoSec #Malware #Microsoft #MicrosoftEdge #MicrosoftTeams #OTX #OpenThreatExchange #Outlook #PowerShell #Python #RAT #RansomWare #SocialEngineering #Windows #bot #AlienVault

  20. When Microsoft's Documentation Conflicts With Testing

    The documentation says shared channels don't support cloud attachments - that's not what I saw.

    #M365 #MicrosoftTeams #Purview #eDiscovery

    newsletter.mikemcbride365.com/

  21. When Microsoft's Documentation Conflicts With Testing

    The documentation says shared channels don't support cloud attachments - that's not what I saw.

    #M365 #MicrosoftTeams #Purview #eDiscovery

    newsletter.mikemcbride365.com/

  22. Microsoft Teams Direct Routing SIP endpoints test

    In this post, I would like to highlight that Microsoft has scheduled a “24-hour test that switches Microsoft Teams Direct Routing SIP endpoints to certificates issued by a new Certificate Authority (CA)” as communicated via the Microsoft 365 Message Center MC1387525.

    Starting June 30, 2026 (9:00 AM UTC), Microsoft will run a test lasting up to 72 hours due to staged regional rollout to transition Direct Routing SIP endpoints to new CA-issued certificates. This aims to improve certificate lifecycle management and maintain secure connectivity. During the test window, organizations using Session Border Controllers (SBCs) for Teams Direct Routing may experience a mix of old and new certificates, as traffic is gradually migrated. If SBCs do not trust the required Root CAs, TLS connection failures may occur, which could lead to disruptions in PSTN calling. So ensure you certificates, certificate chains etc. are alright on your Teams Direct Routing SBCs.

    The change will be applied automatically by Microsoft and reverted after the test period. Organizations are required to proactively verify and if necessary update SBC trust stores, inform relevant voice and support teams, and closely monitor connectivity and TLS handshake behavior throughout the test to mitigate potential service impact.

    Resources

    #Calling #DirectRouting #MicrosoftTeams #SBC #Telephony
  23. What's New in Office 365, Tuesday, June 23, 2026
    8 new posts across 7 Microsoft websites since Friday, June 19, 2026

    #Microsoft365 #Office365 #MicrosoftTeams #SharePoint #PowerBI

    • Exchange Team Blog (1)
    • SharePoint Blog (1)
    • Microsoft Security Blog (2)

    ..and more: o365.cannell.org/2026/06/23/wh

  24. What's New in Office 365, Friday, June 19, 2026
    27 new posts across 15 Microsoft websites since Tuesday, June 16, 2026

    #Microsoft365 #Office365 #MicrosoftTeams #MicrosoftAzure #PowerBI

    • Microsoft Azure Blog (1)
    • Microsoft Defender for Office 365 (1)
    • Access Blog (1)

    ..and more: o365.cannell.org/2026/06/19/wh

  25. heise+ | c’t-Umfrage zu Videokonferenzsoftware: Teams-Alternativen erwünscht

    Wir haben heise-Leser gefragt, wie sie Videokonferenzsoftware verwenden. Tausende haben geantwortet, nur ein Viertel von ihnen entkommt MS Teams.

    heise.de/hintergrund/c-t-Umfra

    #EU #IT #MicrosoftTeams #Journalismus #Videokonferenz #news

  26. Attackers Weaponize Microsoft Teams Relays to Stay Hidden

    Pulse ID: 6a3225be7d5c73fa21d33c57
    Pulse Link: otx.alienvault.com/pulse/6a322
    Pulse Author: Tr1sa111
    Created: 2026-06-17 04:42:38

    Be advised, this data is unverified and should be considered preliminary. Always do further verification.

    #CyberSecurity #InfoSec #Microsoft #MicrosoftTeams #OTX #OpenThreatExchange #bot #Tr1sa111

  27. Attackers Weaponize Microsoft Teams Relays to Stay Hidden

    Attackers deploying DragonForce ransomware against a major U.S. services firm concealed their command-and-control traffic within Microsoft Teams relay infrastructure using Backdoor.Turn, a custom Go-based remote access trojan. This novel technique leverages anonymous Teams visitor tokens and TURN relay servers to mask malicious communications as legitimate Microsoft traffic. The intrusion lasted one to two months, beginning in December 2025 with exploitation of an SQL server vulnerability. Attackers employed sophisticated defense evasion tactics including DLL side-loading with VirtualBox executables and multiple Bring Your Own Vulnerable Driver techniques. They exploited a previously unknown vulnerability in Huawei's HWAuidoOs2Ec.sys driver, along with several other vulnerable drivers, to terminate security processes at kernel level. The campaign demonstrates DragonForce's evolution into a highly capable ransomware cartel with advanced operational maturity.

    Pulse ID: 6a316151d9ab4af59e56576d
    Pulse Link: otx.alienvault.com/pulse/6a316
    Pulse Author: AlienVault
    Created: 2026-06-16 14:44:33

    Be advised, this data is unverified and should be considered preliminary. Always do further verification.

    #BackDoor #CyberSecurity #ICS #InfoSec #Microsoft #MicrosoftTeams #OTX #OpenThreatExchange #RAT #RCE #RansomWare #RemoteAccessTrojan #SQL #Trojan #Vulnerability #bot #AlienVault

  28. CVE-2026-42835: Teams per Android deixa tokens i credencials a l'abast remot

    CVSS 8.1, Important. Atacant autenticat llegeix la memòria heap de l'app via xarxa — tokens d'autenticació, dades de sessió, credencials en caché.

    🛡️ Sense interacció de l'usuari
    🔹 Complexitat: Baixa
    🔹 Correcció a Google Play Store

    Actualitza ja.

    blog.elhacker.net/2026/06/vuln

    #ciberseguridad #MicrosoftTeams #CVE202642835 #Android