We were unable to load Disqus. If you are a moderator please see our troubleshooting guide.
Hi Simon,
I'm glad that you found my solution helpful, unfortunately I have no plan to migrate the Bot due to lack of time, what I suggest you it's to start from scratch with a new Bot V4 and slowly implement the various features.
regards,
Giuliano
Hi Giuliano,
I found your articles and saw a recording of your presentation on this topic in Madrid.
I'm trying to rebuild your solutionon my dev tentant as I agree to your statement, that it is not helpful that everybody can create teams in a companies tenant.
My company is a late starter on O365 so things have changes on O365 and botframework V4 is present.
Do you plan to migrate your bot code to V4, or do you already have a V4 version of veronica bot?
Kind regards
Simon
Hi Simon,
I'm glad that you found my solution helpful, unfortunately I have no plan to migrate the Bot due to lack of time, what I suggest you it's to start from scratch with a new Bot V4 and slowly implement the various features.
regards,
Giuliano
Really cool!
A Little improvement: You may consider taking Logic Apps instead of Flow, cause Flow isn't a solution for global business processes.https://docs.microsoft.com/en-us/az...
It is perfectly fine to use Flow in this scenario. The runtime for Flow is Logic Apps.
It's ok. Logic Apps having better security management, no need to share credentials between Administrators, enhanced logging, SLA etc.
So yes - Flow is fine. But definitly not perfectly fine.
This is definitely a good option thanks for the feedback
Hi Giuliano,
as me and my company is a late starter in O365 I'm a little late to get your bot code to work with botframework V4. Is a V4 version of veronica bot planned?
Kind regards
bilba