Forum Widgets
Latest Discussions
MDM Work Portal Settings – Android – iOS
Hello Team, Please help me with some questions I have regarding the implementation of my MDM policy on Android and iOS mobile devices. When installing these applications, the following questions arise: Why is "location" required, and why is its activation necessary? It requests permission to access the phone's storage — why is this needed? How is web browsing managed or controlled? Defender asks to activate a VPN — I would like to understand why this is necessary. How does Defender classify the severity level as high, medium, or low, and how is this used to determine whether a device is considered compliant?
Moving from skype to teams does not migrate my chat history
Hello, I have tried to login to teams using my skype username. It prompt me to merge my skype account with my personal email. I clicked yes. it successfully logged me in into Ms Teams. I cannot see my skype chat history into teams and also not all of my contacts are there. I have enabled skype account contacts to sync from Settings => People => Sync contact => Manage but still not all contacts are synced and no chat history at all. Anyone knows how can I import the chat history as well? Thank you in advance
Why doesn't Teams jump to the chat when I click on Chat option and it has a badge count??
Why doesn't Teams jump to the chat when I click on Chat option and it has a badge count?? The Chat option in the menu has a count. let's say 1. Why doesn't it take me directly to the chat. I have to hunt it down between my chats and chat channel trying to find it. This happens very often to me and it's just a waste of my time. This UX should be improved. Every time I click on Chat, take me to the next message directly. Keep doing this until I have read all my messages. The 'Unread' option does something similar. It doesn't take me to the next unread messages. It's a frustrating UX.
Smart Moves Tenant Migration
✅ Do's – Best Practices for a Successful Migration 1. Plan Thoroughly Create a detailed migration roadmap. Include: Scope of migration (Teams, SharePoint sites, permissions, metadata) Timeline and milestones Resource allocation (technical team, stakeholders) Risk assessment and fallback strategies 2. Conduct a Pre-Migration Assessment Use migration tool inventory and reporting tools to: Analyze site structures, content types, and permissions Identify orphaned users, broken links, or unsupported features Determine which Teams and SharePoint sites are active and worth migrating 3. Backup Critical Data Before initiating migration: Use native Microsoft 365 backup tools or third-party solutions Ensure version history and document libraries are backed up Validate backup integrity and accessibility 4. Run Pilot Migrations Test the migration process on a few Teams and SharePoint sites: Validate permission mapping Check for metadata preservation Identify performance bottlenecks or errors 5. Communicate with Stakeholders Notify users and admins about: Migration timelines and expected downtime Changes in access or structure post-migration Support channels for reporting issues 6. Leverage migration tool Features Maximize efficiency by using: Bulk migration tools PowerShell scripting for automation Built-in reports for post-migration validation 7. Document URLs and Site Mappings Maintain a clear mapping of: Source and target site URLs Team names and associated SharePoint sites Any renamed or restructured components 8. Use Site Mapping and Permission Mapping Ensure: Accurate mapping of source sites to target locations Permissions are preserved or reconfigured appropriately External sharing settings are reviewed 9. Inform Users About Tool Limitations Set expectations by clarifying: Migration tool does not migrate custom web parts, third-party apps, or workflows Manual recreation may be needed for unsupported features 10. Prefer PowerShell for Large Migrations For large SharePoint sites or Teams: Use PowerShell module for faster, more reliable migration Schedule scripts during off-peak hours to reduce load ❌ Don'ts – Common Pitfalls to Avoid 1. Don’t Skip Inventory Creation Without a content inventory: You risk missing critical libraries, lists, or permissions Migration may be incomplete or inconsistent 2. Don’t Ignore Site Architecture Preserve: Internal links between pages and documents Nested folder structures and navigation menus Custom views and web part configurations 3. Don’t Rush the Migration Avoid: Skipping validation steps Overlooking user feedback Migrating without proper testing 4. Don’t Neglect Metadata Ensure: Version history, authorship, and timestamps are retained Document properties are mapped correctly Metadata is not overwritten or lost 5. Don’t Overlook Security and Compliance Review: Sensitivity labels and compliance policies External sharing settings Access controls and audit logs 6. Don’t Use Vague Naming Conventions Avoid: Duplicate or confusing site/team names Inconsistent naming across tenants Lack of documentation for renamed entities 7. Don’t Use GUI for Large Sites For large-scale migrations: Avoid using the graphical interface Use PowerShell for better performance and error handling 8. Don’t Schedule Incremental Copies During Working Hours To minimize disruption: Run incremental migrations during off-hours Inform users of any temporary access limitations 📌 Summary Thorough Planning and Assessment are key to success. Backup and Testing prevent data loss and uncover issues early. Clear Communication ensures user readiness and reduces confusion. Tool Features and Automation improve efficiency and scalability. Security and Metadata Preservation maintain compliance and data integrity. Avoiding Common Pitfalls ensures a smooth and complete migration.Teams Channels Get Threaded Layout
Many Teams users love to use group chats as a way to get work done. Group chats are effective, but the information shared in chats ends up in personal OneDrive accounts. To help switch people back to channel conversations, Teams has a new threaded layout to make conversations behave much like chats. The new layout works well for some channels but not for others. https://practical365.com/teams-threaded-layout/Can I save all the meetings recordings to a local server
I have a client who wishes to have all their meeting recordings saved to a local server for offline backups and also their policy requires them to have these files locally available. Is there a way that this can be done by automating since it's possible to download the files and trasnfer manually. Was trying to look at the Microsoft Graph but no luck yet. Any help on this will appreciate
Allow muting a person only for me
Sometimes I am in a meeting where one of the persons in the meeting is actually near me in the world outside the screen. In this case the sound is a bit maddening since there is a small delay between the sound from the person and the sound through the teams interface. In these cases, I would like to mute the person only for me since I am sitting near and can hear the person fine without headphones. Right now I need to takeoff headphones when the person is talking and putting it back as the person finishes talking.Native Teams Phone - Background Image
Hello all, Recently Our org. have purchased a few Native Teams Desk phone Poly CCX600 & Conference Trio C60. It appears the default Teams background image, which looks almost blank, after signing in the phone. I followed up the background image document provided by the vendor Poly without luck. Is anyway to modify the background image on these native Teams phones? Your information and support are highly appreciated. Best regards, EZMouse button 'Back/Forward' not working in 'New Teams'
Though there are options to 'pop out' windows from Teams, Teams is a generally a single page app. As such, one of my most used features in 'Classic Teams' is switching back 'n forth between several 'tabs' I'm currently working with. Say I've got somebody on chat, but then have to quickly check something in Teams, then go back to chat. In Classic Teams this works just fine using the mouse's back & forward buttons. In 'New' Teams, this no longer registers any action at all. I assume the feature still exists, since left of the search bar there are still the back/forward UI buttons. But moving the mouse over for every time you need to switch back and forth is a lot slower and less intuitive than just using the mouse buttons. Current behavior: Mouse 'back'/'forward' buttons do not work in 'New Teams' Expected behavior: Mouse 'back/forward' buttons register the 'back' and 'forward' navigation commands as they did in 'Classic' Teams
