Microsoft Teams: New import API and its core benefits you should know about

Continue Reading

Do I need to have a new import API only to import information into Microsoft Teams?

No. You can import information without the new import API too.

There are two methods, using which, we can import the messages. The first method is using the MS Teams import API (Method 1), and another one is the MS Teams Standard API (Method 2). However, there are drawbacks and hurdles you might have to encounter if you perform the migration with the MS Teams Standard API (Method 2). Some of the hurdles are mentioned below

• Unable to retain the original sender in the message as slack
• Unable to retain the slack message posted date and time
• Large scale migration is possible with MS Teams Standard API (Method 2) but it is very time consuming
• Frequent throttling due to heavy data migration

When you go through the long migration process with MS Teams Standard API (Method 2), encountering numerous throttles is common. You’d find it frustrating as there would be a delay in the migration.

Microsoft was aware of this discrepancy and perhaps wanted to bring something that’d bridge the gap and fill the loophole in the migration process, making it faster and more effective. The team worked on it relentlessly and introduced the new functionality that addresses the above issues.

So, how does it benefit and what are its advantages?

One of the most important functionalities would be high throughput processing which means less throttling. The import API supports the following benefitting the users.

• Retention of the actual source message posted time
• Retention of the actual Slack message posted user’s name
• Shows image Inline preview
• No throttles and faster migration

Microsoft has some guidelines to use the APIs and we at AVASOFT ensure that they are strictly followed, and align our services keeping in mind the rules and regulations.