Making Bulk Changes in Microsoft Teams with Confidence<\/h1><\/div>![](\"https:\/\/voss-media.imgix.net\/2023\/01\/Tim-Jalland-Colour-White-border.png?auto=compress%2Cformat&fit=scale&h=768&ixlib=php-3.3.1&w=768&wpsize=medium_large\" "\\"Tim-Jalland-Colour-White-border\\"")
<\/span><\/div><\/div><\/div>Author: Tim Jalland
\nSolution Manager, VOSS Solutions<\/h6>\n
Wednesday September 18, 2024<\/p>\n<\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div>
Using automation and templates to deliver changes efficiently, accurately, and at scale<\/h2><\/div><\/div><\/div>In Microsoft 365 and Teams there\u2019s the regular day-to-day activity that the IT team and Helpdesk need to deal with, as users join and leave, and new service requests are raised. Many customers use the Microsoft Teams Administration Portal to action these changes; this works for the ones and twos, but becomes unworkable for bulk activities – those that might originate from:<\/p>\n
\n- A new department being created<\/li>\n
- A service migration from an older platform \u2013 such as a Cisco PBX<\/li>\n
- Wholesale changes on items such as policies and defaults (perhaps regulatory)<\/li>\n
- A move to a new Microsoft tenant<\/li>\n<\/ul>\n
Either way, these large scale bulk activities often lead into the dark world of PowerShell or elevated Microsoft access permissions, with a need to draw on Microsoft technical resources, but there are better options available. Such as an approach that VOSS recommends, using bulk loading templates to make changes that are:<\/p>\n
\n- Accurate and standardized (based on automation)<\/li>\n
- Secure (without needing broader access rights to Microsoft Teams)<\/li>\n
- Designed for project teams, without the need for deep Microsoft knowledge<\/li>\n
- Tracked (with an audit log)<\/li>\n<\/ul>\n<\/div>
![\"ServiceNow](\"https:\/\/voss-media.imgix.net\/2024\/03\/VOSS-insights-monitoring-resolution-banner.png?auto=compress%2Cformat&fit=crop&h=272&ixlib=php-3.3.1&w=669&wpsize=blog-large\" "\\"VOSS-insights-monitoring-resolution-banner\\"")
<\/span><\/div>Using automation ensures accuracy and standardization<\/h4>\n
VOSS bulk loaders streamline the change process, minimizing errors and simplifying workflows. These loaders can be pre-configured as Excel workbook templates, allowing project teams to efficiently execute bulk changes. This approach ensures quick, repeatable actions without requiring in-depth knowledge of PowerShell or the intricate configuration settings within Microsoft Teams.<\/p>\n
Each VOSS bulk loader can be populated with an input sheet to capture key information (perhaps the names of individuals to be onboarded, or call queues to be configured), along with supplementary sheets to manage each individual setup step: in the case of a call queue, this may involve licensing a resource account, adding a telephone number, and then adding members to the queue.<\/p>\n
Configuration templates further simplify and standardize the setup process. These templates can be created in advance to handle a wide range of complex parameters. For instance, during user onboarding, a template can automatically apply a predefined set of policies, ensuring consistency and efficiency throughout the process.<\/p>\n
Individual rows in the bulk loader can be excluded, enabling selective changes, such as modifying a single line item during initial testing. VOSS bulk loaders can be executed immediately or scheduled for a specific time and date, making them ideal for implementing changes during off-peak hours.<\/p>\n<\/div>
![\"ServiceNow](\"https:\/\/voss-media.imgix.net\/2024\/07\/shutterstock_2167219607-scaled.jpg?auto=compress%2Cformat&fit=crop&h=272&ixlib=php-3.3.1&w=669&wpsize=blog-large\" "\\"Cybersecurity,Concept,Global,Network,Security,Technology,,Business,People,Protect,Personal\\"")
<\/span><\/div>Secure – no need for broader access rights to Microsoft Teams<\/h4>\n
VOSS bulk loaders are managed by members of the project team. Each team member is provided with a suitable VOSS role, with pre-defined privileges that allow them to perform a certain set of changes (for example user onboarding), to a certain part of the organization (perhaps a set of sites). This mitigates the need to provide broad and elevated \u201cTeams Administrator\u201d access across the Microsoft tenant as a whole, to numerous project engineers that come and go.<\/p>\n
Actual changes to Microsoft Teams are performed by the VOSS application, which is registered as a secure application onto the Microsoft tenant using digital \u2018certificate\u2019 authentication – this is recommended by Microsoft as opposed to basic service accounts and authentication with passwords.<\/p>\n<\/div>
Tracked – with an audit log<\/h4>\n
Finally, all changes, whether simple or complex, need to be tracked from an audit perspective. With a VOSS bulk loader running, each individual change is detailed and logged, locally in the applications log, or if needed, out to an audit server (with Syslog).<\/p>\n
Finally, sample VOSS bulk loaders are available from the VOSS team, or may be exported from the application itself.<\/p>\n<\/div>
- <\/i><\/span>
<\/span><\/div><\/div><\/div>Author: Tim Jalland
\nSolution Manager, VOSS Solutions<\/h6>\n
Wednesday September 18, 2024<\/p>\n<\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div>
Using automation and templates to deliver changes efficiently, accurately, and at scale<\/h2><\/div><\/div><\/div>In Microsoft 365 and Teams there\u2019s the regular day-to-day activity that the IT team and Helpdesk need to deal with, as users join and leave, and new service requests are raised. Many customers use the Microsoft Teams Administration Portal to action these changes; this works for the ones and twos, but becomes unworkable for bulk activities – those that might originate from:<\/p>\n
\n- A new department being created<\/li>\n
- A service migration from an older platform \u2013 such as a Cisco PBX<\/li>\n
- Wholesale changes on items such as policies and defaults (perhaps regulatory)<\/li>\n
- A move to a new Microsoft tenant<\/li>\n<\/ul>\n
Either way, these large scale bulk activities often lead into the dark world of PowerShell or elevated Microsoft access permissions, with a need to draw on Microsoft technical resources, but there are better options available. Such as an approach that VOSS recommends, using bulk loading templates to make changes that are:<\/p>\n
\n- Accurate and standardized (based on automation)<\/li>\n
- Secure (without needing broader access rights to Microsoft Teams)<\/li>\n
- Designed for project teams, without the need for deep Microsoft knowledge<\/li>\n
- Tracked (with an audit log)<\/li>\n<\/ul>\n<\/div><\/span><\/div>
Using automation ensures accuracy and standardization<\/h4>\n
VOSS bulk loaders streamline the change process, minimizing errors and simplifying workflows. These loaders can be pre-configured as Excel workbook templates, allowing project teams to efficiently execute bulk changes. This approach ensures quick, repeatable actions without requiring in-depth knowledge of PowerShell or the intricate configuration settings within Microsoft Teams.<\/p>\n
Each VOSS bulk loader can be populated with an input sheet to capture key information (perhaps the names of individuals to be onboarded, or call queues to be configured), along with supplementary sheets to manage each individual setup step: in the case of a call queue, this may involve licensing a resource account, adding a telephone number, and then adding members to the queue.<\/p>\n
Configuration templates further simplify and standardize the setup process. These templates can be created in advance to handle a wide range of complex parameters. For instance, during user onboarding, a template can automatically apply a predefined set of policies, ensuring consistency and efficiency throughout the process.<\/p>\n
Individual rows in the bulk loader can be excluded, enabling selective changes, such as modifying a single line item during initial testing. VOSS bulk loaders can be executed immediately or scheduled for a specific time and date, making them ideal for implementing changes during off-peak hours.<\/p>\n<\/div>
<\/span><\/div>Secure – no need for broader access rights to Microsoft Teams<\/h4>\n
VOSS bulk loaders are managed by members of the project team. Each team member is provided with a suitable VOSS role, with pre-defined privileges that allow them to perform a certain set of changes (for example user onboarding), to a certain part of the organization (perhaps a set of sites). This mitigates the need to provide broad and elevated \u201cTeams Administrator\u201d access across the Microsoft tenant as a whole, to numerous project engineers that come and go.<\/p>\n
Actual changes to Microsoft Teams are performed by the VOSS application, which is registered as a secure application onto the Microsoft tenant using digital \u2018certificate\u2019 authentication – this is recommended by Microsoft as opposed to basic service accounts and authentication with passwords.<\/p>\n<\/div>
Tracked – with an audit log<\/h4>\n
Finally, all changes, whether simple or complex, need to be tracked from an audit perspective. With a VOSS bulk loader running, each individual change is detailed and logged, locally in the applications log, or if needed, out to an audit server (with Syslog).<\/p>\n
Finally, sample VOSS bulk loaders are available from the VOSS team, or may be exported from the application itself.<\/p>\n<\/div>
- <\/i><\/span>
In Microsoft 365 and Teams there\u2019s the regular day-to-day activity that the IT team and Helpdesk need to deal with, as users join and leave, and new service requests are raised. Many customers use the Microsoft Teams Administration Portal to action these changes; this works for the ones and twos, but becomes unworkable for bulk activities – those that might originate from:<\/p>\n
- \n
- A new department being created<\/li>\n
- A service migration from an older platform \u2013 such as a Cisco PBX<\/li>\n
- Wholesale changes on items such as policies and defaults (perhaps regulatory)<\/li>\n
- A move to a new Microsoft tenant<\/li>\n<\/ul>\n
Either way, these large scale bulk activities often lead into the dark world of PowerShell or elevated Microsoft access permissions, with a need to draw on Microsoft technical resources, but there are better options available. Such as an approach that VOSS recommends, using bulk loading templates to make changes that are:<\/p>\n
- \n
- Accurate and standardized (based on automation)<\/li>\n
- Secure (without needing broader access rights to Microsoft Teams)<\/li>\n
- Designed for project teams, without the need for deep Microsoft knowledge<\/li>\n
- Tracked (with an audit log)<\/li>\n<\/ul>\n<\/div><\/span><\/div>
Using automation ensures accuracy and standardization<\/h4>\n
VOSS bulk loaders streamline the change process, minimizing errors and simplifying workflows. These loaders can be pre-configured as Excel workbook templates, allowing project teams to efficiently execute bulk changes. This approach ensures quick, repeatable actions without requiring in-depth knowledge of PowerShell or the intricate configuration settings within Microsoft Teams.<\/p>\n
Each VOSS bulk loader can be populated with an input sheet to capture key information (perhaps the names of individuals to be onboarded, or call queues to be configured), along with supplementary sheets to manage each individual setup step: in the case of a call queue, this may involve licensing a resource account, adding a telephone number, and then adding members to the queue.<\/p>\n
Configuration templates further simplify and standardize the setup process. These templates can be created in advance to handle a wide range of complex parameters. For instance, during user onboarding, a template can automatically apply a predefined set of policies, ensuring consistency and efficiency throughout the process.<\/p>\n
Individual rows in the bulk loader can be excluded, enabling selective changes, such as modifying a single line item during initial testing. VOSS bulk loaders can be executed immediately or scheduled for a specific time and date, making them ideal for implementing changes during off-peak hours.<\/p>\n<\/div>
<\/span><\/div>Secure – no need for broader access rights to Microsoft Teams<\/h4>\n
VOSS bulk loaders are managed by members of the project team. Each team member is provided with a suitable VOSS role, with pre-defined privileges that allow them to perform a certain set of changes (for example user onboarding), to a certain part of the organization (perhaps a set of sites). This mitigates the need to provide broad and elevated \u201cTeams Administrator\u201d access across the Microsoft tenant as a whole, to numerous project engineers that come and go.<\/p>\n
Actual changes to Microsoft Teams are performed by the VOSS application, which is registered as a secure application onto the Microsoft tenant using digital \u2018certificate\u2019 authentication – this is recommended by Microsoft as opposed to basic service accounts and authentication with passwords.<\/p>\n<\/div>
Tracked – with an audit log<\/h4>\n
Finally, all changes, whether simple or complex, need to be tracked from an audit perspective. With a VOSS bulk loader running, each individual change is detailed and logged, locally in the applications log, or if needed, out to an audit server (with Syslog).<\/p>\n
Finally, sample VOSS bulk loaders are available from the VOSS team, or may be exported from the application itself.<\/p>\n<\/div>
- <\/i><\/span>