Portal Known Issues & Guidance

We are aware of an issue when a user signs into an account to accept AUP and set security questions. Users follow the process and upon clicking 'Save', the page loads before an error is shown reading 'Error. An error has occurred while processing your request.

There is a known issue around LA’s not being able to update User Policies in Portal as the receive an error stating ‘There are only #” licences available for this organisation, a maximum of # users can be added to the policy’. This prevents LA’s from performing any updates to User Policies including adding licenses or users.

We are aware of an issue that has been occurring when blank updating a user within a GP phone User Policy in Portal, their mailbox size is being reverted to 4GB as opposed to matching the mailbox size dictated by that User Policy specifically when larger mailbox is toggled on. These GP Phone User Policies were manually created in the database and were not created through the Portal UI which is causing the conflict.

This error is encountered when trying to create a new user with the same first and last name, as an already existing user for that organisation that has no local ID set.

If there are missing Approve/Reject Action buttons if open Static/Dynamic Distribution List via Profile area

If an account locks it can take several minutes to reflect in the Portal

When creating a team via Portal, intermittently below error occurs. The team is then created in the tenant, but not in Portal.

We are aware of accounts going into a deleting status after a delete operation is performed.

This is currently a known issue for owners of distribution lists only, this does not affect Local Administrators.

We are aware of an issue when an owner of a Distribution List makes a change to the DL properties by either adding a member, where there is over 250 members already, this will require going for Local Admin approval to the Organisation.

By design Portal allows you to create multiple Virtual Visit Bookings with the same name.

We are currently seeing an issue with users’ data is showing incorrectly between Portal and AD/Exchange. A user may have updated their name and email address successfully in Portal but those changes have not been replicated in AD/ Exchange causing a data mismatch.