iPckger Documentation
iPckger logo

Tenant(s)

Tenant(s)

Overview

With iPckger’s Team and Enterprise tiers, you can add more than 1 tenant. Team members can access one or more Microsoft 365 tenants, ensuring efficient collaboration while maintaining security.

Adding a new Tenant

Go to the tenant(s) page

  1. Navigate to Menu > Tenant(s).
  2. Press the Add Tenant button.
  3. Fill in the necessary information: Client ID, Tenant ID, and Client Secret.
  4. Then click on the Create Tenant button.

Managing Tenant(s)

Command Description
Test connection Tests the connection to Azure to make sure the filled in information is correct.
Team members Makes it possible to add team members to the tenant, this way you can assign tenant(s) to yourself or other team members. This then will be visible on the deployment page.
Edit Makes it possible to edit client ID, tenant ID, and client secret
Delete tenant Deletes the specific tenant only in iPckger and removes all the managed packages iPckger deployed.

Managing Tenant Access

Team members can be granted access to specific tenants. To edit access:

  1. Navigate to Menu > Tenant(s).
  2. Press the 3 dots Team members.
  3. Adjust tenant access by adding or removing a team member.

Removing a member’s tenant access revokes their ability to manage apps in that tenant immediately.

INFO

Please review the assigned tenants carefully before saving to ensure permissions remain accurate.

Setting your default scopetag.

If you have an Enterprise license, you can deploy using a scope tag .

  1. Navigate to Menu > Tenant(s).
  2. Press the 3 dots Team edit.
  3. Adjust your scopetag to the default needs.

BE AWARE:

Want to let your team members choose a scope tag each time they deploy? Just toggle the radio button to "Let my team members choose the scope tag".

If you don’t enable this, team members will be required to deploy using the default scope tag that you’ve configured. This can be useful if you're managing a centralized deployment process within a single Azure tenant.

However, if you're the root admin and managing deployments across multiple departments or sub-organizations within a larger Azure tenant, it’s considered best practice to allow team members to select their own scope tag. This ensures flexibility and prevents accidental deployments to unintended environments.

Extra Information

Can a member belong to multiple teams?

No. Each user can only join one team per subscription.