MC1113665 – Physical badging Connector new sample power shell script (archived)

Product:

Purview, Purview Communication Compliance, Purview Insider Risk Management

Platform:

Online, US Instances, World tenant

Status:

Change type:

Feature update, Admin impact

Links:

Details:

Summary:
Microsoft has updated the Microsoft Purview Physical Badging Connector to enhance security. Organizations using this connector must download and apply a new PowerShell script by June 30, 2025, to maintain functionality. Separate scripts are available for Commercial, GCC, GCCH, and DoD environments. No UI or workflow changes are expected.

Details:
What and Why
To support the continuous improvement of security standards, Microsoft has updated components of the Microsoft Purview Physical Badging Connector. These updates ensure that Insider Risk Management customers can continue securely uploading physical access data. Organizations using this connector must apply the updated PowerShell script to maintain functionality.
Rollout Schedule
This update was released on June 30, 2025.
Impact on Your Organization
Who is affected:
Organizations using Microsoft Purview Insider Risk Management with the Physical Badging Connector in any environment (Commercial, GCC, GCCH, DoD).
What will happen:
The previous PowerShell script used to upload physical badging data will no longer function.
A new PowerShell script must be downloaded and applied to continue uploading data.
Separate scripts are available for Commercial, GCC, GCCH, and DoD environments.
No changes to UI or user workflows are expected.
Action Required / Recommendations
To ensure uninterrupted data uploads:
Download the updated PowerShell script for your environment:
Commercial GitHub script
GCC GitHub script
GCCH GitHub script
DoD GitHub script
Apply the updated script in your organization.
Communicate this change to your security and compliance teams.
Update any internal documentation referencing the previous script.
Administrators can set up a data connector to import user data from their organization to insider risk management policies.
Compliance Considerations
No compliance considerations identified, review as appropriate for your organization.

Change Category:
XXXXXXX ... free basic plan only

Scope:
XXXXXXX ... free basic plan only

Release Phase:

Created:
2025-07-12

updated:
2025-07-12

Task Type

XXXXXXX ... free basic plan only

Docu to Check

XXXXXXX ... free basic plan only

MS Preperations

XXXXXXX ... free basic plan only

MS Urgency

XXXXXXX ... free basic plan only

MS workload name

XXXXXXX ... free basic plan only

summary for non-techies**

XXXXXXX ... free basic plan only

Direct effects for Operations**

PowerShell Script Functionality
Failure to apply the new PowerShell script will result in the inability to upload physical badging data, disrupting data flow and compliance processes.
   - roles: IT Administrators, Compliance Officers
   - references: https://github.com/microsoft/m365-physical-badging-connector-sample-scripts/blob/master/push_physical_badging_records.ps1

Data Upload Interruption
Without the updated script, organizations will face interruptions in data uploads, potentially leading to gaps in insider risk management and security oversight.
   - roles: Security Analysts, Data Managers
   - references: https://github.com/microsoft/m365-physical-badging-connector-sample-scripts/blob/master/push_physical_badging_records_gcc.ps1

Internal Documentation Updates
Organizations will need to update internal documentation referencing the previous script, which may lead to confusion and miscommunication if not managed properly.
   - roles: Documentation Specialists, IT Support Staff
   - references: https://github.com/microsoft/m365-physical-badging-connector-sample-scripts/blob/master/push_physical_badging_records_ITARL4.ps1

Configutation Options**

XXXXXXX ... paid membership only

Opportunities**

Automated Script Deployment
Implementing a centralized automation tool for deploying PowerShell scripts can streamline the update process for the new Physical Badging Connector script across various environments. This reduces manual errors and ensures consistency in application.
   - next-steps: Evaluate automation tools such as Azure Automation or System Center Configuration Manager (SCCM) to facilitate script deployment. Train IT staff on the selected tool.
   - roles: IT Administrators, Security Teams, Compliance Teams
   - references: https://docs.microsoft.com/en-us/azure/automation/automation-overview, https://docs.microsoft.com/en-us/mem/configmgr/, https://techcommunity.microsoft.com/t5/itops-talk-blog/automate-your-powershell-scripts-with-azure-automation/ba-p/1382270

Enhanced Documentation and Training
Updating internal documentation and providing training sessions on the new PowerShell script will ensure that all relevant teams are informed and can operate effectively with the new system. This minimizes disruptions and enhances user experience.
   - next-steps: Create a comprehensive training module and update internal documentation to reflect the changes. Schedule training sessions for IT and compliance teams.
   - roles: IT Administrators, Compliance Teams, Training Coordinators
   - references: https://www.microsoft.com/en-us/microsoft-365/blog/2021/05/25/empowering-people-with-the-skills-they-need-to-succeed/, https://www.sans.org/blog/documentation-and-training-best-practices-for-incident-response/

Monitoring and Reporting Enhancements
Integrating monitoring solutions to track the deployment and performance of the new PowerShell script can provide insights into usage patterns and potential issues. This can lead to proactive troubleshooting and improved operational efficiency.
   - next-steps: Assess current monitoring tools and consider integrating solutions like Azure Monitor or Power BI for reporting on script execution and performance metrics.
   - roles: IT Administrators, Security Teams, Operations Managers
   - references: https://docs.microsoft.com/en-us/azure/azure-monitor/overview, https://powerbi.microsoft.com/en-us/, https://techcommunity.microsoft.com/t5/azure-monitor-blog/monitoring-powershell-scripts-in-azure-automation/ba-p/2142955

Potentional Risks**

XXXXXXX ... paid membership only

IT Security**

XXXXXXX ... paid membership only

explanation for non-techies**

XXXXXXX ... free basic plan only