TechIDManager.EntraID 5.441/5.425! Don’t worry, everything is still backward compatible. This is the integration between TechIDManager and EntraID, formerly called TechIDManager.AzureAD. The name change reflects Microsoft’s name change for the same thing. Install instructions are https://ruffiansoftware.com/entraid-azure-ad-install-instructions-primary-secondary/.
This version runs differently than previous versions. This runs on a single Azure tenant with the “Base” installation on a consumption plan that does all the processing and execution. This is usually the MSPs tenant. This reaches into the multiple other tenants with the “Linked” installations. These are usually the MSP’s clients’ tenants (without the requirement for a subscription). There are specific security reasons for this architecture.
This version maintains support for pure EntraID environments and support for hybrid DC/EntraID environments with AD Connect already setup and running to sync users. We suggest a non-hybrid setup for admin users.
If you are using this script to update an installation, basically run the appropriate script and it will check for an existing installation and ask if you want to update it, or if you want to convert it to a “Base” or “Link” installation.
If you want the Base installation tenant to also be an agent to manage accounts, then you need to run the Link installation on it, too. Contact Support@TechIDManager.com with any questions.
This version changes:
- Single Base installation via PowerShell Script with Azure CLI to an Azure Tenant with a subscription.
- Multiple Linked installations via executable that uses Azure CLI to an Azure Tenant that do NOT require subscriptions, including possibly the same tenant that has the Base installation.
- To update, only the Base installation needs to be updated.
- Both the Base and Linked installs can run on GCC/GCC-High Azure.
Instructions (shortened version of https://ruffiansoftware.com/entraid-azure-ad-install-instructions-primary-secondary/)
- Install the Azure CLI on your computer.
- The latest Azure CLI is recommended, there have been issues with older Azure CLI installs causing the installation script to fail.
- Download the Base script to your computer.
- Open a PowerShell window and run the Base deploy script
- When prompted, login to the Azure Tenant that will be running as the Base. This tenant requires a subscription, and is usually the MSP tenant.
- Answer all the questions and say yes to making it a Base installation
- Download the Linked installation application to your computer.
- Extract the zip file a folder
- Change directory into that folder with the PowerShell window
- Run TechIDManager.EntraID.Installer.exe
- When prompted, login to the Azure Tenant that will be a Linked installation. This tenant does not require a subscription, and is usually the client’s tenant.
- Answer the questions, if updating an existing installation, then say yes to convert to a Linked installation. Once the Linked installation is complete you can delete the Resource Group that was the legacy install.
Deploy_TechIDManager_EntraID_5.441.ps1 Installation Script for Base Install (NOTE* you probably need to right click and “Save link as”) This should only be installed in one (1) EntraID Tenant. Original style installations can also be done with this script, too.
TechIDManager.EntraID.Installer_version_5.425x64server_Release.zip Installation application for Linked installations. This should be installed in all EntraID Tenants where accounts should be created and maintained.
Change Log for pre-release
Base 5.425 -> 5.441
- Support for WordList Password Style
- Support for forced password rotation
Both 5.407 -> 5.425:
- Primary renamed to Base
- Secondary renamed to Link
- Support for Base also being a Link
- Link install script clean up
Secondary 5.400 -> 5.407:
- Handle install issue with Secondary tenants with no subscriptions
Primary 5.392 -> 5.403:
- Fixed concurrency issue in Primary
Secondary 5.399 -> 5.400:
- Better y/n answer handling.
Secondary 5.398 -> 5.399:
- Secondary installer typo in new install questions.
- Handle subscriptions without access
Secondary 5.392 -> 5.398:
- Secondary installer support for multiple Azure CLI copies installed.
Primary/Secondary 5.391 -> 5.392:
- Support for older Azure agent conversion to secondary
- Better error messages
- Editing changes for agent options in MC
Primary/Secondary 5.383 -> 5.391:
- Fix bug in secondary install related to graph urls for updating
- better error messages
As always, if you have any questions or issues, contact Support@TechIDManager.com
