Office 365 Outlook activity not working after deployment

[morz3d]

Hi,
Is someone experiencing a problem with Office 365 Outlook activity after deploymeny is done via deployment pipelines or via saving as in different workspace.

In my case I can see Sing in page however clicking on button doesnt work.

There is problem if i try to run this pipeline i get "InternalServerError executing request"
Problem is solved if I delete outlook activity.
Anyone else facing this problem?

[DanielSDavis]

Any progress on this?  I'm using GIT integration and it seems that when you create an Outlook activity at adds a section to the pipeline item for logicAppsConnectionPayload.  The subscription that is created behind the scenes is specific to the object and workspace, so naturally when you deploy it to another workspace it overwrites the subscription with one that isn't valid causing you to have to re-authenticate.

I know this is in "preview", but it seems just about 90% of Fabric is preview.  A way around this would be ideal.  We need to be able to promote changes without having to reauthenticate Every. Single. Time.

[DanielSDavis]

Been able to find a work-around for this.  It seems that authorizing an Office 365 activity creates a resourceGroup and subscription in Azure behind the scenes which is specific to the activity and it's workspace.  Since the GIT deployment just pushes the entire JSON, this includes the entire "logicAppsConnectionPayload" section

"logicAppsConnectionPayload": {
            "id": "/subscriptions/########-####-####-####-############/resourceGroups/connections-########-####-####-####-############/providers/Microsoft.Web/connections/1_########-####-####-####-############_########-####-####-####-############",
            "properties": {
                "api": {
                    "name": "office365",
                    "id": "/subscriptions/########-####-####-####-############/providers/Microsoft.Web/locations/eastus/managedApis/office365"
                }
            }
        }

Understandably the subscriptions in your Dev workspace aren't valid for UAT and Production, so when you commit the JSON file in it's entirety it overwrites the previously working subscription with one that isn't authorized.  If you authorize after-the-fact it alters the JSON causing the higher environment to show it's no longer in sync.

If you're like me, you can't even sync it after the fact in production, because the branch doesn't allow pushing directly (only through PRs)

Fortunately.... Fabric doesn't need this section of the JSON to function.  It's just a reference.  If you delete this section from the JSON (View --> Edit JSON code) After you have authorized, saved, and refreshed your screen then save again it wont commit the section to your repository.  You have to do this in each workspace and every time you make a change to ensure it doesn't stop working.

My advice..... Create a dedicated pipeline for emails and use parameters.  Deploy it once and call the pipeline within other pipelines to use it.  Then the only time you should have to mess with it is to update credentials.

[morz3d · Accepted solution]

Hi @Anonymous 
Different browser didnt work, however workaroud that worked for me was following:

1. Delete existing Outlook activity (avoid saving)
2. Add new one, for that one you would be able to sign in (avoid saving)
3.  reload page so your old Outlook activity is back, and it will be connected and paramtrized as it should

[AdamFry]

Thank you so much for posting this, I have the exact same problem.  My data pipeline in the development stage is working fine to send an error email when any failures or problems are identified.  When I use a deployment pipeline to send my data pipeline to the test stage, I get the InternalServerError executing request if I try to run the data pipeline that got deployed.  After a lot of troubleshooting, I was able to identify that it was the email activity causing the problem.  I could get my pipeline to run in the subsequent stages by deleting the email activity but I couldn't find any way to sign in.  Clicking the sign in button would do nothing.  Deleting the email activity and then readding it allowed me to sign into my email service account and click "allow access".  Then closing the pipeline and discarding the changes worked to keep the email activity setup with all the properties it got from the deployment pipeline.  

Is this just a manual step that you do each time you run your deployment pipeline?  I'm not sure there's any good way to automate this.  

[ReginaldPenguin]

Hi,

We were having this issue, also took a huge effort to find the culprit as there's no helpful information to lead you to that conclusion at all.

Now we appear to be having a similar issue. Is the Outlook acitivity fit for use?

[Anonymous]

Hi @morz3d ,

It was great to know that you were able to get to a resolution . We expect you to keep using this forum and also motivate others to do that same . You can always help other community members by answering to their queries

[Anonymous]

Hi @morz3d ,

Thanks for using Fabric Community.

When I tried to repro your scenario, I didn't observe any issue.

It looks like an intermittent issue. Can you please retry it again after clearing browser cache?
Also can you please try in different browsers like Edge, Chrome, etc?

Please let me know if you are still facing the issue.