> For the complete documentation index, see [llms.txt](https://docs.realmjoin.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.realmjoin.com/ja/zi-dong-hua/runbooks/runbook-references/org/security/list-expiring-role-assignments.md).

# 期限切れ間近のロール割り当てを一覧表示

まもなく期限切れになる Entra ID のロール割り当てを一覧表示

### 説明

選択した日数以内に期限切れとなる、アクティブおよび PIM 対象の Entra ID ロール割り当てを一覧表示し、期限内に更新できるようにします。各項目には、ロール、プリンシパル、期限日が表示されます。変更は加えられません。

### 場所

組織 → セキュリティ → 期限切れ間近のロール割り当てを一覧表示

**完全な Runbook 名**

rjgit-org\_security\_list-expiring-role-assignments

### 詳細

| プロパティ    | 値                                   |
| -------- | ----------------------------------- |
| バージョン    | 1.0.1                               |
| 必須モジュール  | RealmJoin.RunbookHelper (>= 0.8.10) |
| スケジュール可能 | いいえ                                 |

### 権限

#### アプリケーションのアクセス許可

* **種類**: Microsoft Graph
  * RoleManagement.Read.All
    * *ロール割り当てスケジュール、資格スケジュール、およびロール定義を読み取ります*
  * User.Read.All
    * *各割り当てのプリンシパルを /users/{principalId} 経由で UPN に解決します*

### パラメーター

#### 日数

この日数以内に期限切れとなる割り当てが一覧表示されます。

| プロパティ   | 値          |
| ------- | ---------- |
| 必須      | false      |
| 既定値     | 30         |
| 種類      | Int32      |
| ポータル表示名 | 期限切れまで（日数） |

[Runbook リファレンスの概要に戻る](/ja/zi-dong-hua/runbooks/runbook-references.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.realmjoin.com/ja/zi-dong-hua/runbooks/runbook-references/org/security/list-expiring-role-assignments.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.