Azure Bot Service (Microsoft Bot Framework) vs. Google Authenticator

It is suited for applications like computerizing messages, or any business thought that would require the entrepreneur to robotize their reactions, particularly assuming they are managing a ton of clients and they can't answer to every single one of them. It'd be the most ideal to computerize messages of enormous associations where the reactions measure up to the clients' assumptions. It would be less appropriate in associations where clients' viewpoints matter and every client is interesting and requires the association's consideration, where the specialist organization doesn't need to sum up the clients' interests.

It is supported by virtually all cloud-based software applications for business. I am happy to allow users to use this in addition to other authenticators. Certainly, if your business is in the Google cloud it makes sense, but my approach to the remote/virtual work world these past couple of years has been structured flexibility. Leaving some choice up to the users for their own comfort, particularly when they are using their own devices. I cannot think of a scenario where it is less appropriate - perhaps where you run the risk of "app sprawl". I.e., where you are requiring users to handle multiple authenticators (which can happen with certain pieces of hardware) you may want to encourage consolidation into one to avoid frustration.

Incentivized

• Real-time communication.
• Lightweight software protocols.

Incentivized

• One strength is in how it checks identity to stop unwanted people from getting access.
• Another strength is in cutting down on the frustration of users for the authentication process.
• With the pandemic and needing to work away from the office it also provided additional security in keeping our network/infrastructure safe.

Incentivized

• They have simplified the coding for the bot in Azure, but it would help if the coding was further simplified so that non-IT can operate [and] create it easily.

• I once performed a factory reset of my smartphone which had Google Authenticator. I didn't have a backup for the device. When I restored my phone with the same google account, I was not able to restore the authenticator app settings. I had to add all the keys back into the app to use it. This is cumbersome, but I understand it is set up this way for security reasons.
• I don't like the ease with which it lets you delete a key. If I accidentally delete a key, I am doomed to get my 2FA key reset, unless I still have the QR code saved somewhere.

Incentivized

It works as intended, easy to setup, free and gives you another level of security against any unwanted access or cyber attacks

Incentivized

Azure Bot Service provides an integrated environment for bot development. Microsoft Azure Cloud is fully compatible and its security features. It's more important to pay attention to the logic of business than the specifics of each messenger. We don't have any issues using the bot framework because the implementation is excellent.

Incentivized

I have not faced any technical challenge personally using this application. It's very lightweight and doesn't require many system resources on your mobile device.

Incentivized

In terms of availability, I had not experienced any issues with outages or the product not working when needed

Incentivized

The performance of google Authenticator is good and I have not experienced any slow downs

Incentivized

Support is helpful when we have a problem, but online documentation is lacking

I have found Google’s support to be hit or miss. There are times when they are very responsive, and I get my issue resolved quickly, and there are times where a response from them takes weeks. There is no in-between. But my support experience with this particular product is nonexistent because I have not had a problem with it yet. Hopefully, we do not have any problems with it either.

Incentivized

It was easy to implement and it went very smoothly. No issues

Incentivized

Microsoft Bot Framework is much better and well more established without a lot of proprietary software/coding language. Lex is very limited with integration with standard hardware and network configurations. Lex has performance issues and was too slow to meet near real-time collaboration requirements. Bot Framework complements many other Microsoft communication products and this was key to implementing without a lot of new training required.

Incentivized

We deploy Google Authenticator in residential and non-managed client scenarios. Google Authenticator can perform the basic functions needed for multi-factor authentication but lacks the more advanced features of solutions like Cisco's Secure Access by Duo. Google Authenticator is our go-to solution for anyone ready to increase their security but struggling to find the necessary technology budget.

Incentivized

The product doesn’t have any features of tools that can help it scale

Incentivized

• Interfaces with the SQL data set, tracks down plans/replies, and tests them with the SDK.
• Utilizing the system is made conceivable by the Bot Dev gateway. We can interface our bot in excess of ten channels, including Twilio Facebook, Twilio, Twilio, and Slack, and that's only the tip of the iceberg.
• It is expensive.

• More secure data = less worried about a data breach.
• Takes longer to log in, and if I don't have my phone then I have to go looking for it, so it really makes it so that you can't be without your phone, which in certain instances is annoying or not possible and can hold up work time.
• Everyone is willing to use the same program because everyone likes Google—makes it easier to manage.

Incentivized