已预配Teams标签应用CI/CD部署提示未预配问题求助

问题描述 #

开发基于Teams标签的应用时，本地通过Teams Toolkit可正常部署至多环境，且各环境对应的state.(envname).json文件已签入代码库。但在Azure DevOps中配置CI/CD流水线时，明明目标环境已完成预配，却反复收到**“资源未预配”**的错误提示。已确认流水线环境变量配置正确，且服务主体可正常访问Azure，问题仍未解决。

流水线YAML配置 #

trigger:
# When new commits are pushed onto the main branch.
- main 

pool:
  vmImage: ubuntu-latest

steps:
# Setup environment.
- task: NodeTool@0
  inputs:
    versionSpec: '14.17.0'
    checkLatest: true

- task: DownloadSecureFile@1
  name: envFile
  inputs:
    secureFile: '.env.teamsfx.test'

- task: CopyFiles@2
  inputs:
    SourceFolder: $(envFile.secureFilePath)
    Contents: '**'
    TargetFolder: 'tabs'

- task: Bash@3
  env:
    # To enable M365 account login by environment variables and non-interactive mode.
    M365_ACCOUNT_NAME: $(M365_ACCOUNT_NAME)
    M365_ACCOUNT_PASSWORD: $(M365_ACCOUNT_PASSWORD)
    M365_TENANT_ID: $(M365_TENANT_ID)
    CI_ENABLED: 'true'
    TEAMSFX_ENV_NAME: test
  inputs:
    targetType: 'inline'
    script: |
      set -evuxo pipefail
      
      # Install the local dev dependency of @microsoft/teamsfx-cli. 
      # 'npm ci' is used here to install dependencies and it depends on package-lock.json.
      # If you prefer to use 'npm ci', please make sure to commit package-lock.json first, or just change it to 'npm install'.
      npm ci

      # Build the project.
      # The way to build the current project depends on how you scaffold it.
      # Different folder structures require different commands set.
      # 'npm ci' may be used here to install dependencies and it depends on package-lock.json.
      # If you prefer to use 'npm ci', please make sure to commit package-lock.json first, or just change it to 'npm install'  

      cd tabs; npm ci; npm run build; cd -;

      # Login Azure by service principal
      npx teamsfx account login azure --service-principal --username $(AZURE_SERVICE_PRINCIPAL_NAME) --password $(AZURE_SERVICE_PRINCIPAL_PASSWORD) --tenant $(AZURE_TENANT_ID)

      # Deploy to hosting environment.
      npx teamsfx deploy --env ${TEAMSFX_ENV_NAME}

错误信息 #

> ) [core] failed to get questions for deployArtifactsV2: Failed to deploy because the resources have not been provisioned yet. Make sure you do the provision first. Click Get Help to learn more about why you need to provision.
(✖) [Solution.CannotDeployBeforeProvision]: Failed to deploy because the resources have not been provisioned yet. Make sure you do the provision first. Click Get Help to learn more about why you need to provision.
(✖) Get help from https://aka.ms/teamsfx/whyneedprovision#SolutionCannotDeployBeforeProvision
##[error]Bash exited with code '255'.

排查方向与解决方案 #

1. 检查State文件的加载路径 #

Teams Toolkit在CI环境中依赖项目根目录.fx文件夹下的状态文件识别预配资源。

• 确认.gitignore未排除.fx目录，Azure DevOps流水线的checkout步骤也未添加该目录的排除规则；
• 在Bash步骤中添加调试命令，验证状态文件是否存在：

  ls -la .fx/state.test.json
  

2. 修正环境配置文件的复制路径 #

当前流水线将.env.teamsfx.test复制到tabs目录，但Teams Toolkit要求环境配置文件放在.fx/env.test路径下。修改CopyFiles任务：

- task: CopyFiles@2
  inputs:
    SourceFolder: $(envFile.secureFilePath)
    Contents: '.env.teamsfx.test'
    TargetFolder: '.fx/env.test'
    OverWrite: true

3. 对齐Teams Toolkit CLI版本 #

本地与流水线使用的CLI版本不一致可能导致状态文件解析逻辑冲突。在脚本中指定与本地一致的CLI版本：

# 替换为本地使用的版本号，例如2.0.0
npx @microsoft/teamsfx-cli@2.0.0 account login azure --service-principal --username $(AZURE_SERVICE_PRINCIPAL_NAME) --password $(AZURE_SERVICE_PRINCIPAL_PASSWORD) --tenant $(AZURE_TENANT_ID)
npx @microsoft/teamsfx-cli@2.0.0 deploy --env ${TEAMSFX_ENV_NAME}

4. 验证服务主体权限 #

确保服务主体拥有目标资源组的Contributor或更高权限，且流水线中AZURE_TENANT_ID与资源所在租户ID完全一致，避免跨租户访问导致的资源识别失败。

内容的提问来源于stack exchange，提问作者cwhd