The deployment profile is set to ignore filegroups placement, but the generated change script is still creating indexes on specific filegroups. Using a dacpac created from an existing database as a source and a different database as a target, the change script generated has create index statements on filegroups that do not exist on the target database. As a workaround, the filegroups can be created on the target databases via a different process, but I would have assumed that this should not be necessary as it was already specified in the deployment profile to ignore filegroup placement.
