search

microsoft / BotFramework-Services

Microsoft Bot Framework Services
Creative Commons Attribution 4.0 International
38 stars 11 forks source link

Don't have access to my bots from Bot Framework Portal #346

Closed amaroRafael closed 2 years ago

amaroRafael commented 2 years ago

Issue Description When I go to My Bots at Bot Framework Portal I can't find my bot.

Bot info of one of the already registered and working but now missing bots: Bot Id: CINOLATeamsApp-local-debug App ID: cb636e51-f9b3-49c6-8b94-66ad1a514d24 SDK Platform: .NET

The email that was associated is '@gome.ai'

breakingram commented 2 years ago

Hi @amaroRafael

Checking with engineers on this issue and will report back soon. Thanks.

moooyo commented 2 years ago

Hi @amaroRafael

we confirmed your information and found you submitted a request of clean up your privacy data to us. So, we removed you from the bot's owner list. This change usually occurs when someone leaving the organization. Can we confirm that what happened in 8/31/2022 12:00:26 AM(UTC)?

amaroRafael commented 2 years ago

Hi @moooyo

Thanks for replying to me.

Let me explain the situation. My account was in two organizations, two different tenants. And I removed this account from one of the tenants. However, the tenant that I left was not the same tenant who is the owner of the bots. So, it shouldn't have removed me from the bots.

I can provide you with the tenant ids to confirm this information if you need it.

boydc2014 commented 2 years ago

Hi, @armaansood. I apologize for the inconvenience for the situation. We've identified an issue around handling tenant information when a data clean up request is triggered and we are working on a fix for it. But unfortunately, we can't simply bring it back for you as our process requires a little bit confirmation to recover your ownership.

I would suggest two options

  1. If your current tenant have a valid azure subscription. I recommend you go to azure portal and recreate a new "Azure Bot" and enable Teams channel. In fact, bot record is just a piece of metadata and you can easily point the new bot record's endpoint to your bot app (local or remote). Azure portal is a more modern and standardized solution which tracks resource ownership in tenant level than dedicated portal (dev.botframework.com) which tracks ownership by individual owner id.
  2. If you really need that bot back. I'm afraid you have to use the owner email to send us an request to recover the ownership. You will need to cc your tenant's admin and get his\her approval and send it to bfwktriage@microsoft.com.

I will recommend the first approach. Apologize again for this issue.

amaroRafael commented 2 years ago

Hi @boydc2014

I was the bot owner, sometimes I also add my Manager as the owner of bots, but I don't remember if I included him this time. Can you at least let me know if there is any email of the owner included that is from "@gome.ai"? If it doesn't have any email there, this means that I was the only owner of this bot.

About the 1. suggestion. When I use the Teams Toolkit, it will auto-create the bot in botframework.com. If that bot is not there, when I try to run the project in Visual Studio, it will fail and say that I need to run the [Teams Toolkit] -> [Prepare Teams App Dependencies]

How can I solve this issue?

I am developing the project in Visual Studio 2022. This is a C# project

boydc2014 commented 2 years ago

Hi, @amaroRafael our log shows you were the only owner, thus there is no owner right now after clean up.

About suggestion 1. Yes, the approach you were using is basically Teams Studio calling Azure Bot Service(which is us) creating the record for you using your identify (individual identity) in dev.botframework.com and enabling Teams channel for that bot. The functionality is the same when Teams creating it for you or you choose to create your bot by yourself in Azure Portal. It's the same service and feature sets.

In Azure Portal, the benefit is the resource ownership is tracked via tenant/subscription instead of individuals. The cost is you have to create via Azure Portal by yourself. I recommend this approach for the long run.

The missing part is ownership to the metadata in service side, it's agnostic to which client language or IDE you use.

If you only doing local debugging, the most straightforward way is to re-create another bot, or to be specific, bot registration. The bot registration should be lightweight and easy to recreate. You bot code written with VS is you bot app itself, which can work with any registration if you get the configuration aligned. Does that make sense?

amaroRafael commented 2 years ago

Hi @boydc2014 ,

Is it possible to remove this bot from botframework.com so I can use the same application to create a new bot? I am asking this because we have an environment where this application is already in use by some users.

boydc2014 commented 2 years ago

Hi @boydc2014 ,

Is it possible to remove this bot from botframework.com so I can use the same application to create a new bot? I am asking this because we have an environment where this application is already in use by some users.

Yes, @amaroRafael we can do that. Can you help send a email with the original owner email (assume you still hold) to bfwktriage@microsoft.com and we can do the clean up

boydc2014 commented 2 years ago

Bot has been cleaned up.