[CoE Starter Kit - BUG] Upgrade failure due to "Solution dependencies exist, cannot uninstall." ObjectName: Office 365 Management API

[Jenefer-Monroe]

Does this bug already exist in our backlog?

• I have checked and confirm this is a new bug.

Describe the issue

We have removed the Office 365 Management API custom connector from Core and so you may see if this failure on upgrade

You will not be able to upgrade again until you complete these steps, described in detail below.

1. Delete _upgrade
2. Delete Audit Logs solution and any other dependencies
3. Try your upgrade of Core again
4. Setup new Audit Logs collection technique using either (a) new HTTP methodology or (b) a copy of the old technique.

1. Delete _upgrade

First delete the failed upgrade solution
Note you may need to browse to solution install history and back before you see it.

Note also the deletion may timeout, you will need to watch in the history for it to complete

2. Delete Audit Logs

First delete the Center of Excellence - Audit Logs solution itself.
This should remove the majority of the dependencies straight away.

Spot check for dependencies
Some people have found that some objects do not get deleted when the old Audit logs solution gets deleted so just go double check that they did and delete these objects if you see them still there.
Go to the Default Solution > Connnection References.

Use Power Shell to check for straggler connections
Some people have found that there are still references to the connector remaining that they cannot see in the UX and hence have to use powershell to find and delete these remaining connections to the old connector.

It will look something like this:
Get-AdminPowerAppConnection -EnvironmentName [Guid]

Remove-AdminPowerAppConnection -ConnectionName [ConnectionName] -ConnectorName shared_twitter -EnvironmentName Default-[Guid]

3. Try your upgrade of Core again

Now you can now reinstall the new Core release. Please look for failures and _upgrades which would indicate you are still broken due to straggler connections.

4 a. Setup new Audit Logs collection technique

Now that you have upgraded to a modern version of Core components, if you want to re-establish Audit Log collection for App Launches, you need to do that as shown here

The steps outlined in Collect audit logs using an HTTP action describe how to do it. But one note for those of you migrating from old to new technique is how to change your app registration.

How to update app registration

1. Browse to your app registration.
2. API Permissions > Remove the delegated permissions to Office 365 Management APIs ActivityFeed.Read

3. Add instead Application permissions to Office 365 Management APIs ActivityFeed.Read and get it granted for the organization
   

Complete setup
Then from here, complete the rest of the steps outlined in Collect audit logs using an HTTP action

4 b. OH NO I CANT USE THE NEW TECHNIQUE HELP!

If you cannot use the new methodology, perhaps you cant get the application permissions on the app registration, you can still use the old technique although it will not be something we can assist with going forward.
Please follow the steps in this issue: #6017
It also contains some solutions you can use to get going.

[Yocomd]

I have run into this issue, but am unable to delete the _upgrade solution due to dependencies.

Any suggestions?

[albertocastro365]

Hi,
i have this issue also (I didn't see the instructions of upgrade to this version).

In my case I will start to use Data Export, the after delete the _upgrade solution, I also delete the Audit Logs solution, but this issue keeps in a new import of the core 4.13 solution.

[Jenefer-Monroe]

@albertocastro365 can you please post a separate issue? This way we dont confuse the situations across people.
And please as you do so, share a screenshot of the state of your solutions so I can see what is currently installed.

[Yocomd]

I was able to get around my issue by following the instructions to delete the old Audit Log solutions (6009) and then choosing Apply Upgrade on my version 4.11 core solution. That completed the upgrade and deleted the 4.11 solution, so all that remains is 4.13.

[jaredwsimmons]

Hi, i have this issue also (I didn't see the instructions of upgrade to this version).

In my case I will start to use Data Export, the after delete the _upgrade solution, I also delete the Audit Logs solution, but this issue keeps in a new import of the core 4.13 solution.

I think I've found what the error message is complaining about. There may be a Connection Reference in your previous Core Components solution that is pointing at your Office 365 Management API Custom Connector... go in there and delete it (I was able to at least thru the Default solution) and then delete the Custom Connector itself from your environment. Retry the import and let us know.

[SPMush]

Hi, i have this issue also (I didn't see the instructions of upgrade to this version).
In my case I will start to use Data Export, the after delete the _upgrade solution, I also delete the Audit Logs solution, but this issue keeps in a new import of the core 4.13 solution.

I think I've found what the error message is complaining about. There may be a Connection Reference in your previous Core Components solution that is pointing at your Office 365 Management API Custom Connector... go in there and delete it (I was able to at least) and then delete the Custom Connector itself from your environment. Retry the import and let us know.

Many thanks jaredwsimmons
I had converted to collecting logs via http back in June (and removed the Audit log solution) but was still getting the error.
Within the Default Solution connection references, as you suggested, there was indeed an Office 365 management API reference still there.
Deleting it then allowed me to delete the deprecated Office 365 management API custom connecter.
Core upgrade to 4.13 was then successful and the uninstall of 4.11 completed without error.
👍

[declawson]

Still can't upgrade from Core Components 4.11 to 4.13 still saying it can't install because of the O365 Management API Connector.
I have done the following:
Modified the API Permissions in App Registration from Delegated to Application
Exported/Imported data from the Compliance Center
Removed the Audit Log solution
Removed the O365 Management connector
Deleted the Core Component Upgrade solution and then imported again
Tried to Apply Upgrade to 4.11 Core Components
Core Component 4.13 Upgrade - shows no dependencies
Core Component 4.11 - still shows O365 Management API Custom Connector as a dependency

[declawson]

Thanks for pointing me back to #6270 . I had already performed these but someone commented about deleting the O365 Management API connector from the Default solution. Deleted from default and redid Apply Upgrade which worked.
Thanks Again!

[Jenefer-Monroe]

thanks for letting me know here, that will help others as well!