Assess the change against the use case and the risk you accepted. A provider update may alter output quality, available controls, data handling, or how an integration behaves. Keep a record of the versions you can identify, review available change notices, and decide which checks need to be repeated before wider use. If the provider does not offer version control or adequate notice, account for that limitation in your operating plan. Not every change requires a full new audit, but a material change should not pass unnoticed simply because the feature name and subscription stayed the same.
Related: SOC 2 audit and compliance hub.
Further reading: NIST Generative AI Profile.