Deployment fails with a media service error in northcentralus

[sdsd-dsd]

FYI - when I tried to deploy to LOCATION="northcentralus" I got the following error for the media service:

{
    "status": "Failed",
    "error": {
        "code": "BadRequest",
        "message": "Creation of new Media Service accounts are not allowed as the resource has been deprecated.",
        "details": [
            {
                "code": "MediaServiceAccountCreationDisabled",
                "message": "Creation of new Media Service accounts are not allowed as the resource has been deprecated."
            }
        ]
    }
}

Changing to LOCATION="eastus" deployed without errors.

[dayland]

Thank you @sdsd-dsd. I have opened an internal ticket for this. We were aware the Media Services were planning to be deprecated, but were unaware it had already been put into effect in some regions.

[georearl]

Media Services is scheduled for 30th June 2024. This is the guide. On deeper investigation Video Indexer, which is the service we use that sits on top of Media Services, will switch away from this before the end date....

Is Azure Video Indexer being retired?
No, Azure Video Indexer isn't part of the Media Services retirement. Although Video Indexer currently relies on a Media Services account as part of its workflow, this dependency will be eliminated before Media Services is retired on June 30, 2024. See the following for more information: impact of Media Services retirement for Video Indexer.

As of today, Video Indexer still requires a Media Services service to be created, and so we can't remove it from bicep deployment. We will need to assess closer to the date if VI is working without the service and we can then remove the dependency.

As noted in the issue, the error above is interesting as it seems to indicate the media service cannot be created. This is not the case, it does work in regions where VI and Media Services are available. I have updated this to an enhancement and we will add a ticket to the board to action this when VI can be deployed without this supporting service.

[dayland]

Duplicate of #501

[lelong-adm4soa]

Hello, I have run into this issue with new deployments. It appears the block went into place the end of Jan 2024 for New media Services, noted in the guide posted. Any news on the fix?

Edit, I just checked #501. I am checking my fork to re-deploy

[georearl]

This has been addressed with a PR in main - you should not be seeing issues now if you pull latest