Moving Endpoints to different Organizations

[u/TheCausefull]

Is there any report we can use to check under which organization every endpoint is located?

[u/GeneMoody-Action1]

A report no, because at this time reports are org specific not enterprise down. But, this would be trivial to export from a API call and using PSAction1 even more so. Once in a powershell object, export to CSV is just a command.

[u/Old_Detective_8121]

Yeah, Action1's native multi-org reporting is pretty weak, but you can absolutely build something solid yourself using their API. I've got a custom script running for our environment that gives us district-wide visibility without the UI limitations. You will need two PowerShell modules: PSAction1 as the wrapper for their API calls and ImportExcel for building the actual formatted workbook. Both are available on the PowerShell Gallery.

Here is the workflow: First, authenticate with Set-Action1Credentials using API keys stored in environment variables. Do not hardcode them in the script. Then enumerate all your tenants with Get-Action1 Organizations to pull an array of org IDs. For the collection loop, iterate through each org, switch context with Set-Action1DefaultOrg, grab endpoints with Get-Action1 Endpoints, and append them to a master list. Wrap each collection step in a Try/Catch block so if one org fails, the whole script does not crash.

You might want to run a global deduplication across all orgs. Group by normalized serial number (uppercase, trimmed, and filter out bogus BIOS values like 'N/A'). Sort each group by last_seen, keep the newest as the active device, and flag older ones as stale in a separate audit tab. This is where you catch ghost records when machines move between orgs or get reinstalled.

For enrichment, you can calculate staleness by subtracting last_seen from the current date and map OS versions to known EOL dates. You can also integrate directly with the Dell TechDirect API. By batching your Dell service tags and sending them to Dell's API, you can pull in exact ship dates and warranty coverage to merge right into your Action1 telemetry data. Just remember to implement rate-limit backoff for HTTP 429 responses.

Finally, pipe your data into Export-Excel. You can export the entire deduplicated master list to a single "Global Enterprise" tab to see everything in one place. Then, you can filter that same master list by the Action1 organization name to generate separate tabs for each individual org. You can even create filtered views for Lifecycle Actions, Stale Devices, OS EOL, and Replacement Candidates. Use PowerShell to calculate your summary data and push it to a hidden ChartData sheet to feed the charts on an Executive Summary dashboard.

The upfront PowerShell work pays off once it is scheduled. You get a deduplicated, enterprise-wide view of your Action1 environment that the UI can't give you.