Microsoft have introduced a new automated user number status report for Operator Connect.

This enables us to automatically provision DDI with relevant call plan for the below 2 scenarios:

How this works (for assigned users):

1. DDI is assigned to a user via Teams Admin Center.
2. Number assignment status report is generated by Microsoft’s Operator Connect automation.
3. If an “Unassign” plan was previously provisioned for a given DDI, NTT DATA will automatically apply the most affordable call plan from the customer’s contract.
4. The updated number call plan will be reflected in the NTT DATA Cloud Voice App every 36 hours*.

How this works (for unassigned users):

1. DDI is unassigned via Teams Admin Center (i.e., user leaves the organization).
2. Number assignment status report is generated by Microsoft’s Operator Connect automation.
3. NTT DATA will automatically apply the “Unassigned call plan” to the DDI.
4. The updated number call plan will be reflected in the NTT DATA Cloud Voice App every 36 hours*.

*Automatic number synchronization will be enhanced once the implementation of this new feature is confirmed as stable.

A new release was published on July 13th 2024.

• Introduce the Porting Status and Porting Date (Firm Order Commitment - FOC Date) in the Cloud Voice Preview APIs
  This allows our partners using APIs to display the porting status and date in their applications
  API User guide

A new release was published on February 10th 2024.

Updates:

• Add the area code requirement for Canada and Japan numbers ordering
• Other technical improvements and minor bug fixing

We are pleased to announce a new release published on October 07th, 2023.

The main new features are:

• Cost code & Calling Plan Bulk upload activity
  When using the feature cost code and calling plan bulk update a new log is created and visible in the activity section.
  The activity is now in a more readable format.
  
  
  
  
  
• Other
  • Bug fixing

We are pleased to announce a new release published on September 09th 2023.

The main new features are:

• Calling plan bulk update using Excel export/import
  This provides the ability to update calling plans and cost codes using the bulk update feature that was dedicated to cost codes only before.
  
  
  
  
  
  
• Other
  • Implemented the way to handle different document templates for a single country based on Number Type for porting
  • Same Microsoft Tenant can be used by multiple Billing Accountss for a single Customer
  • Other bug fixing

We are pleased to announce a new release published on August 12th 2023.

The main new features are:

• Support system migration
  Due to support system migration, some disturbances have occurred in the past days.
  The orders created pre-migration and post-migration are all visible now.
  High priority is given to continue improving this user interface experience.
  
  
  
   

• Other
  • Porting Management: introducing new API endpoint for Porting Constrain for all countries
  • Porting Management: validate during port request using new endpoint
  • Ordering and porting for Japan: area code become mandatory and tooltip is updated
  • Ordering and porting for  USA and Canada: CNAME tooltip updated
  • Other bug fixing
     
    
    

We are pleased to announce a new release published on June 24th 2023.

• New Cloud Voice APIs
  New Cloud Voice APIs are available for Billing Account and Subscription management. This allows to create, add, change or remove items from a subscription for example.
  Contact your Account Manager to get API access.
  
  
• Cost codes
  Up to 1500 values per cost code are now possible (500 before)
  
  
• The Cloud Voice Application is now called “Cloud Voice” in the list of Apps and Services of the NTT Services Portal.
  
  
• Cloud Voice App menu keeps open initially when coming from the main Services Portal

We are pleased to announce a new release published on May 13th 2023.

The main new features are:

• Porting Time selection
  You can now only select porting time according to the country specific constraints (minimum duration requirements, business hours).
  
  
• Application Name differentiation between Microsoft Teams Direct Routing and Operator Connect
  For customers who are having both Teams Direct Routing and Operator Connect, the numbers' list now shows both options.

We are pleased to announce a new release published on April 8th 2023.

The main new features are:

• Portal access
  Your Cloud Communications admin portal becomes an application of our NTT Ltd. Services Portal.
  When coming from the url portal.arkadin.com you are now automatically redirected to portal.global.ntt
  
  
• Wherever the site/location is displayed, the full address is now also displayed
• Wherever the destination group is displayed, a description is now also displayed
• Service numbers can be ordered per 1 unit except for Singapore (per 10 units)
• Other smaller improvements and bug fixes
  

We are pleased to announce a new release published on March 11th 2023.

The main new features are:

• Cloud Communications Application becomes Cloud Voice Application
  The Cloud Communications Application now exclusively available from NTT Ltd. Services Portal has been renamed Cloud Voice.
  During few month and to avoid Customer misunderstanding the suffix “(ex-Cloud Communications)” is added.

• Application Menu updates
  The left, top and right menus/panels, are now using the Services Portal styling and aligns with its Theme (dark or light).
  Application Menu items have been renamed to be aligned with the application new name.

• Global/Local user accounts
  The Billing Account setup that you use to manage in the Cloud Communication application can now be managed from the Access Management application of the Services Portal.
  
  
  
  
  
• Number ordering minimum quantity
  For most of European and Asian countries a minimum quantity of 10 consecutive numbers was mandatory when ordering numbers. With the exception of Germany, this requirement is not applicable anymore.
  
  
• Draft Order and Porting 
  When coming back to a draft order or porting request, the previous context is pulled so that the user will go to the latest step-1. This will avoid having to navigate form the initial step each time.