Limite de geração de imagens é consumido mesmo sem entrega visual

Evan Elias 0 Reputation points
2026-05-28T03:59:18.6533333+00:00

Ao tentar gerar uma imagem com o Copilot, percebi que o limite de uso foi contabilizado mesmo quando nenhuma imagem foi exibida no card. Isso gera uma experiência negativa, pois o usuário sente que está “gastando créditos” sem receber nada em troca.

Impacto:

  • Usuários podem perder tentativas de geração sem resultado.
  • Clientes pagantes ficam em desvantagem, já que o limite é consumido sem benefício.
  • A experiência causa frustração e desconfiança no produto.

Sugestão de melhoria:

O sistema deveria diferenciar tentativas bem-sucedidas de falhas. Se não houver entrega de imagem, o limite não deveria ser consumido. Isso garantiria transparência e confiança no uso do recurso.

Microsoft Copilot | Other
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest

  1. AI answer

    2026-05-28T03:59:33.59+00:00

    AI image generation features in Copilot and Microsoft 365/Windows apps use a credit-based model where each generation attempt consumes a credit, regardless of whether the user ultimately keeps or sees a satisfactory image.

    From the documented behavior:

    • AI credits are the unit used to measure use of AI features such as generating or editing images in Microsoft 365 and Windows apps (Designer, Paint, Photos, etc.). Each AI action (for example, generating a set of images) consumes credits automatically as soon as the request is processed, not only when the result is visually accepted or used.
    • For Image Creator in Paint, each time a set of images is generated, one AI credit is spent. Credits are deducted when the generation request is handled, and notifications are sent only when credits are low or exhausted, not based on whether the user is satisfied with the output.
    • For Copilot and AI tools in the broader platform (for example, AI Builder/Copilot Studio image or text tools), consumption is similarly tied to the processing of the request (for example, “per image” or “per page”), not to successful user acceptance of the result.

    The current documentation does not describe any differentiation between “successful” and “failed” generations for credit charging, nor any automatic refund when no image is ultimately shown or used. Credits are consumed by the attempt itself.

    Given this, the described behavior—credits being consumed even when no image is effectively delivered—is consistent with the documented “per action/per image” charging model, but it does create the negative experience described.

    To address this in practice:

    1. Capture the scenario details (where the image was generated: Copilot in Microsoft 365, Paint Image Creator, Designer, etc.; time, account type, and whether any error message appeared).
    2. Open a support case via the appropriate channel (for example, Microsoft 365 support or Windows support) so engineering can:
      • Review whether there was a transient service or content-filtering failure that prevented the image from being displayed.
      • Confirm whether credits were correctly or incorrectly deducted in that specific case.
    3. Share the improvement suggestion (only charge on successful delivery or refund on failure) in the same support ticket or via product feedback channels so it can be considered for future changes to the credit model and UX.

    The product team can then investigate whether this is a bug (for example, generation blocked by content filtering or service issues but still charged) or expected behavior under current limits, and whether adjustments to charging or error handling are needed.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.