💡We automated the provisioning steps in a PowerShell script for you. It will connect to our environment and get the needed changes applied to your infrastructure.

Microsoft Graph PowerShell Permissions

Script Overview

Below is an overview of the steps performed by our provisioning script

Provisioning - Step by Step

Script download

Get the provisioning script via direct link below. Pick the link depending on the chosen location:

✅ TENANT ADMIN To execute the script Tenant Administrator credentials must be provided (→ 'Global administrator' role). 

🔍 Refer to the diagram above for an overview. During execution and depending on pending Service Settings changes the script will perform the steps below:

• Connect to Microsoft Graph, Microsoft Teams and your Nimbus tenant.
• Grant the needed consent for the main Nimbus application, this will allow Nimbus to read user and team details in the tenant and record voice messages if the latter is configured for the team. → See: Required App Permissions
• Create, update or delete an Application Instance and grant the required consent to it to be able to set up conversations.
• Associate or remove Phone System license 🔍 Refer to Installation Prerequisites > PSTN licensing for details.
• Apply an Online Voice Routing Policy from the ones defined and selectable on your tenant. This is only required for Nimbus services which are using a Direct Routing phone number.
• Add, update or delete PSTN phone number. ☝ Note that a PSTN number causes additional license cost by Microsoft. Get in touch with your local O365 integrator.
• Lastly the script will apply Service Settings - either new or future changes made by you or any service team owners (e.g. a name, UPN, or phone number change).

Script Execution

1. Execute the script and wait for the connection to Microsoft Graph, Teams, and Nimbus. 💡 If the script is not up-to-date you will be requested to download the latest version.
2. When requested to login, provide your tenant admin credentials

3. You may be asked for your admin consent on the first run of the script. 💡When using a Global Admin account you can grant these Permissions for your entire organization, so other administrators do not need to repeat this step.

• If this has already been done by a tenant admin in the Nimbus Installation chapter, this is not required again.
• Potentially missing calling bot permissions (required e.g., for establishing sessions and posting Adaptive Cards to your Teams) will also be regranted automatically.

5. ⮑ The Script now checks whether any Nimbus services have been added, changed in the respective Service Settings , or deleted since the last time the script was run. 
   6. All services with pending changes will be shown as either Delete, Create or Update. You can then choose one of the two options.
   • I - per Team individually - you can inspect and confirm each change.
   • A - for all Teams - all changes are auto-confirmed. ☝ Please note that PSTN licenses will be applied automatically as long as they are available - first come, first serve base.
6. Carry on with the next step for further technical details.

PSTN Licenses and Voice Policies

Script Conclusion and Rerun

When everything runs as expected you will see green DONE indicators and the script finishes.

💡 At the end you will be asked if you want to rerun the script:

1. You want to keep the script instance open until all Service changes are complete, so you don't need to authenticate again.
2. For each further pending change in the General Service Settings (e.g. in dialog with your Service Team Owners) the PowerShell instance can be run again until you are satisfied with the results.

Verifying changes via Test Call

To test the call functionality: 

1. Ensure that team members (service users) are Available for the called team and be set to Active in their Nimbus Dashboard.
2. Open General Service Settings on the service you want to test.
3. Click on Test Call → The UPN of the service will now be called via Team Client.

💡 You can test this with 2 different Microsoft Teams client accounts in separate browser windows to simulate this call on your own as both caller and recipient.

💡 If you have assigned a PSTN license / phone number to the service it is also recommended to test calling it.

PSTN Limitations

INC Transfer to PSTN Limitation

TRANSFER TO PSTN LIMITATION

Out of the box, Nimbus and related addons can only perform PSTN transfers according to Microsoft's licensing and constraints.

Which PSTN license do I need to acquire?

As of 2023, "Microsoft Teams Phone Standard" licenses are no longer supported by Microsoft. Previously, those licenses were viable for Nimbus. Regardless if you are using Direct Routing, Calling Plans, Operator Connect, the "Microsoft Teams Phone Resource Account" license is now always required. 

Your Setup	Required License
Direct Routing	"Microsoft Teams Phone Resource Account"
Calling Plan	"Microsoft Teams Phone Resource Account" + "Microsoft Teams Domestic Calling Plan" or "Microsoft Teams Domestic and International Calling Plan" or "Microsoft Teams Calling Plan pay-as-you-go" + "Communication Credits" (if these aren't already included as part of your plan)
Operator Connect	"Microsoft Teams Phone Resource Account"

☝Please note that Luware staff cannot give recommendations on which license plan is best suited for your needs. Depending on your scenario, additional Teams App licenses may be required. Exact details are to be discussed with your Microsoft contacts.

---

^{Also see: https://learn.microsoft.com/en-us/microsoftteams/teams-add-on-licensing/virtual-user}

 

 

How does PSTN licensing affect service and call transfers?

Assuming that Service A has a PSTN license assigned - but further Services don't - the following scenario may unfold:

Scenario A - Service A workflow is configured to transfer the caller to Service B. The license of Service A is used, the PSTN transfer occurs. The PSTN license is re-used throughout further transfers to Services C...D…x…and so on.

Scenario B - Service B is called directly instead. Now the workflow of Service B attempts a redirect to either service A or transfer to C. The PSTN transfer fails due to a missing license on Service B.

🌟Learnings:

• For one first-level-response service: If you handle first-response calls always via the same service, you need a PSTN license for that particular first-level service.
• For multiple first-level-response services: If you handle first-response calls always via multiple services, you need a PSTN license for all those first-level services .
• Nimbus will attempt to use the PSTN license of the first service that responded to a call, regardless of how many further internal service transfers are performed thereafter.
• If no PSTN license is found on a service that requires it for a transfer, the transfer task will be considered as failed and treated accordingly by the system (e.g. workflow exit announcement, reporting "transfer failed" outcome).

 

 

☝Note that handling and tracking of running cost for PSTN licenses is outside of the Luware support scope. If you require assistance in extending and/or configuring your Nimbus services for PSTN, our support will gladly assist you:

Luware Support Address

Luware Website	https://luware.com/support/
Luware Helpdesk	https://helpdesk.luware.cloud
Cloud Service Status	https://status.luware.cloud/

 

 Troubleshooting & Known Issues