Breakout Troubleshooting
Hi everyone - hoping you're well. I have issues when organising events where there are presenters (who have cameras enabled) and participants (cameras and mics disabled). Once presenters finish - we want them to join breakout rooms to have discussions. The issue is - the cameras do not turn on in the breakout rooms. I enable them from the options before sending people into breakouts - their mics turn on but no cameras. Has anyone found a solution to this please?
Teams and Sharepoint Architecture and practices
Hi all, My organization is at the beginning of developing our SP online-based intranet and we want to incorporate and use Teams as a primary way of driving projects and possibly creating long term Team sites for our departments. Before we go too far, we want to make sure that we have an appropriate architecture and possible "workflows" (not Workflow) to ensure that documents are available and record management is as easy as possible. We have identified multiple ways that we can see published pages making available major documents (perhaps an approved policies) developed by a group using a Team site. For instance, do you link from the published site to the teams doc? Do you migrate the final products or even libraries to an intermediate collaboration site? Do you move the products or even the libraries to the site with published pages? Does anyone know of a "best practices" to support Teams integrated SP search, metadata consistency, indexing, records management and such? I have read that Teams flattens the architecture and I see why. But I also see difficulties with each option. So any experience, suggestions or resources that are available would be helpful.
Azure RBAC Custom Role Best Practices or Common Build Patterns
As a platform admin, I want to grant application admins Contributor access while removing their ability to write or delete most Microsoft.Network resource types, with a few exceptions such as Private Endpoints, Network Interfaces, and Application Gateways. Based on the effective control plane permissions logic, we designed two custom roles. The first role is a duplicate of the Contributor role, but with Microsoft.Network//Write and Microsoft.Network//Delete added to notActions. The second role adds back specific Microsoft.Network operations using wildcarded resource types, such as Microsoft.Network/networkInterfaces/*. Application Admin Effective Permissions = Role 1 (Contributor - Microsoft.Network) + Role 2 (for example, Microsoft.Network/networkInterfaces/, Microsoft.Network/networkSecurityGroups/, Microsoft.Network/applicationGateways/write, etc.) I understand that Microsoft RBAC best practices recommend avoiding wildcard (*) operations. However, my team has found that building roles with individual operations is extremely tedious and time-consuming, especially when trying to understand the impact of each operation. Does anyone have suggestions for a simpler or more maintainable pattern for implementing this type of custom RBAC design?
